Commands
The command surface arrives one release at a time. Each release adds its commands here, one page per top-level command, with subcommands on the page of their command.
| Command | Since | Purpose |
|---|---|---|
rigger init |
v0.1.0 | Create the database |
rigger project |
v0.1.0 | Add, list and show projects |
rigger doctor |
v0.1.0 | Show the database path, schema version and record counts |
rigger import |
v0.2.0 | Read a notes hub into versions, tasks and events |
rigger backup |
v0.2.0 | Copy the database aside |
rigger context |
v0.3.0 | Print the context packet for a project |
rigger note, rigger wish |
v0.3.0 | Record an event or a wish |
rigger resolve |
v0.7.0 | Answer a question or sort a wish |
rigger open |
v0.4.0 | Start a Claude Code session with the packet |
rigger mcp |
v0.5.0 | Serve the packet and the recording tools over MCP |
rigger sync |
v0.6.0 | Read tags and commits into facts |
rigger find |
v0.8.0 | Search every project’s events |
rigger why |
v0.8.0 | The work that went into a version |
rigger inbox |
v0.9.0 | Questions waiting for your answer |
rigger digest |
v0.9.0 | What moved lately, five lines per project |
rigger version |
v0.10.0 | Aim a version at a week of the calendar |
rigger calendar |
v0.10.0 | Weeks by projects: planned, shipped, slipped |
rigger next |
v0.10.0 | This week’s focus, and what is behind |
rigger week |
v0.11.0 | The Monday brief: focus, Friday, what waits |
rigger release-day |
v0.11.0 | The shopfront queue: what is out, what waits for Friday |
rigger retro |
v0.12.0 | Planned against shipped, per cycle |
rigger session |
v0.13.0 | Start and end a sitting; the end writes the journal |
rigger export |
v0.14.0 | Write a hub back out of the record |
rigger adopt |
v0.15.0 | Record every repository under a directory, with its hub and its tags |
rigger skill |
v0.15.0 | Write a thin project skill from a template and the record |
rigger profile, rigger task |
planned v0.17.0+ | Switch profiles; find, open and close tasks |
Common to all commands
Section titled “Common to all commands”--versionand--helpon the bare binary;--helpon every command.RIGGER_DATA_DIRoverrides the data directory for every command.--jsonprints the same facts as data, on the commands that show facts.- Exit status is
0on success and1on any failure, with the reason on stderr prefixederror:. Never2, including for a usage error: an assistant’sStophook reads 2 as a refusal to stop, and a mistyped hook must be ignored rather than hold a session open.