@obsfx/trekker 1.2.0 → 1.4.0

package/README.md

@@ -1,6 +1,6 @@
 # Trekker
 
-A CLI issue tracker built for AI coding agents. Stores tasks, epics, and dependencies in a local SQLite database with a built-in kanban board. No server required.
+A CLI issue tracker built for AI coding agents. Stores tasks, epics, and dependencies in a local SQLite database. No server required.
 
 ## Install
 
@@ -24,7 +24,7 @@ My concerns about the future and security of that project led me here. Trekker i
 
 What you get:
 - Task and epic tracking with dependencies
-- Built-in kanban board UI with real-time updates
+- Optional kanban board UI available as a [separate package](https://github.com/obsfx/trekker-dashboard)
 - No special directory required. The .trekker folder stays local to your project.
 - No hook integrations. Just task management.
 
@@ -83,6 +83,7 @@ trekker epic create -t <title> [-d <desc>] [-p <0-5>] [-s <status>]
 trekker epic list [--status <status>]
 trekker epic show <epic-id>
 trekker epic update <epic-id> [options]
+trekker epic complete <epic-id>  # Complete epic and archive all tasks/subtasks
 trekker epic delete <epic-id>
 ```
 
@@ -122,6 +123,53 @@ trekker dep remove <task-id> <depends-on-id>
 trekker dep list <task-id>
 ```
 
+### Search
+
+Full-text search across epics, tasks, subtasks, and comments using FTS5:
+
+```bash
+trekker search <query> [--type <types>] [--status <status>] [--limit <n>] [--page <n>]
+```
+
+Examples:
+```bash
+trekker search "authentication"                          # Search all entities
+trekker search "bug fix" --type task,subtask             # Search only tasks and subtasks
+trekker search "login" --type comment --status completed # Search comments in completed items
+```
+
+### History
+
+View audit log of all changes (creates, updates, deletes):
+
+```bash
+trekker history [--entity <id>] [--type <types>] [--action <actions>] [--since <date>] [--until <date>]
+```
+
+Examples:
+```bash
+trekker history                                  # All events
+trekker history --entity TREK-1                  # Events for specific entity
+trekker history --type task --action update      # Only task updates
+trekker history --since 2025-01-01 --limit 20    # Events after date
+```
+
+### List
+
+Unified view of all epics, tasks, and subtasks:
+
+```bash
+trekker list [--type <types>] [--status <statuses>] [--priority <levels>] [--sort <fields>]
+```
+
+Examples:
+```bash
+trekker list                                     # All items, newest first
+trekker list --type task --status in_progress    # Active tasks only
+trekker list --priority 0,1 --sort priority:asc  # Critical/high priority first
+trekker list --sort title:asc,created:desc       # Sort by title, then by date
+```
+
 ### Web Interface
 
 For a visual kanban board, install the separate dashboard package:
@@ -133,13 +181,26 @@ trekker-dashboard -p 3000  # Start dashboard on port 3000
 
 The dashboard shows tasks grouped by status and reads from the same `.trekker/trekker.db` database.
 
-## JSON Output
+## Claude Code Integration
 
-Add the `--json` flag to any command for structured output:
+For seamless integration with [Claude Code](https://claude.ai/code), install the Trekker plugin:
 
 ```bash
-trekker --json task list
-trekker --json task show TREK-1
+claude /plugin marketplace add obsfx/trekker-claude-code
+claude /plugin install trekker
+```
+
+This gives Claude Code native access to Trekker commands through MCP. The agent can create tasks, update status, and manage dependencies without running CLI commands directly.
+
+See [trekker-claude-code](https://github.com/obsfx/trekker-claude-code) for more details.
+
+## TOON Output
+
+Add the `--toon` flag to any command for structured output in [TOON format](https://github.com/tooners/toon). TOON is a token-efficient serialization format designed for AI agents, using fewer tokens than JSON while remaining machine-readable:
+
+```bash
+trekker --toon task list
+trekker --toon task show TREK-1
 ```
 
 ## Status Values
@@ -175,6 +236,8 @@ Run `trekker quickstart` to see the full guide with best practices for creating
 
 This is my personal workflow for getting the most out of Trekker with AI agents:
 
+- **Install the Claude Code plugin.** I use [trekker-claude-code](https://github.com/obsfx/trekker-claude-code) to give Claude Code direct access to Trekker through MCP. This way, the agent manages tasks natively without running CLI commands.
+
 - **Always mention Trekker in prompts.** I include "use trekker" in my instructions so the agent knows to track its work.
 
 - **Point agents to the quickstart.** I tell the agent it can run `trekker quickstart` to learn how to use Trekker properly. This gives it all the context it needs without me having to explain everything.