rigmode 0.1.1

Attach work modes to AI coding agent prompts
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114

# Usage

## Commands

### `rigmode attach <AGENT>`

Used by the Claude Code `UserPromptSubmit` hook. Reads JSON on stdin, prints `hookSpecificOutput.additionalContext` JSON on stdout.

```sh
echo '{"prompt":"implement this"}' | rigmode attach claude-code
```

Always exits `0` (empty stdout on failure or no match), so Claude Code never erases the prompt.

| Flag | Description |
|------|-------------|
| `--modes-dir <PATH>` | Override `config.toml` modes dirs (repeatable) |

Agent today: `claude-code`.

### `rigmode hook install <AGENT>`

```sh
rigmode hook install claude-code
rigmode hook install claude-code --force   # allow a binary under target/
```

Registers the `UserPromptSubmit` hook in `~/.claude/settings.json` (or `$CLAUDE_CONFIG_DIR/settings.json`). Idempotent on `args`, not the binary path. Then runs `check` and prints warnings without failing. Restart Claude Code after install.

| Flag | Description |
|------|-------------|
| `--force` | Allow registering a binary under `target/` |

### `rigmode hook uninstall <AGENT>`

```sh
rigmode hook uninstall claude-code
```

Removes only the rigmode entry.

### `rigmode check`

```sh
rigmode check
rigmode check --modes-dir ./modes
```

Validates modes and hook registration. Non-zero exit on errors; warnings alone still exit `0`.

| Flag | Description |
|------|-------------|
| `--modes-dir <PATH>` | Override `config.toml` modes dirs (repeatable) |

### `rigmode log`

```sh
rigmode log
rigmode log --mode review --limit 20
```

Lists recorded attaches (newest first) from `attach.jsonl` — the ground truth for which modes a prompt actually received.

Columns: timestamp, attached modes, working directory, session id.

| Flag | Description |
|------|-------------|
| `--mode <NAME>` | Filter by attached mode name |
| `--limit <N>` | Max rows to print |

### `rigmode gate`

```sh
rigmode gate
rigmode gate --mode implement --limit 20
```

Lists recorded interventions (newest first) from `gates.jsonl`.

Columns: timestamp, modes, marker, note, session id.

| Flag | Description |
|------|-------------|
| `--mode <NAME>` | Filter by mode name |
| `--limit <N>` | Max rows to print |

## Gate recording

`gates.jsonl` records interventions only — the moments a human pushed back on the agent's work. Declare intervention words in `config.toml`:

```toml
[gate]
markers = ["wrong", "redo", "that's not it"]
```

When a prompt's **first line** matches a marker (same literal rules as mode triggers) and the session has a prior attach, `attach` appends one line to `gates.jsonl` with the session's last attached modes. An empty list (the default) disables recording. Approvals are not recorded — silence means pass.

## Debugging

```sh
# Validate modes dirs, frontmatter, and hook registration
rigmode check

# Dry-run attach without Claude Code
echo '{"prompt":"implement this"}' | rigmode attach claude-code

# See what actually attached in recent prompts
rigmode log --limit 20

# See recorded pushbacks
rigmode gate --limit 20
```

`attach` always exits `0` and writes logs best-effort. If nothing attaches, check triggers with `check`, then confirm the hook path with `hook install` / `check`.