@staff0rd/assist 0.786.0 → 0.787.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/claude/commands/review-config.md +17 -3
- package/dist/commands/sessions/web/bundle.js +384 -384
- package/dist/index.js +1 -1
- package/package.json +1 -1
|
@@ -27,10 +27,24 @@ Every glob must match files this repo actually has. Check each one does before p
|
|
|
27
27
|
|
|
28
28
|
## Step 3: Put the proposal to the user
|
|
29
29
|
|
|
30
|
-
|
|
30
|
+
Do not ask in chat. Write the proposal as markdown to a scratch file with the Write tool, one heading per key so each can be commented on:
|
|
31
31
|
|
|
32
|
-
-
|
|
33
|
-
- `
|
|
32
|
+
- each glob as its own bullet, with the files in this repo it matches (a count, plus a few names), and why it belongs
|
|
33
|
+
- `descriptionWordCap` with its value
|
|
34
|
+
- the scope you propose, with the other one named so the user can swap it:
|
|
35
|
+
- `project` — the repo's own `assist.yml`, checked in, so the team reviews against the same globs (propose this unless the user has said otherwise)
|
|
36
|
+
- `repo` — this repo's block in `~/.assist.yml`, personal to this machine
|
|
37
|
+
|
|
38
|
+
Then run, **as a background task**, doing no other work until it returns:
|
|
39
|
+
|
|
40
|
+
```
|
|
41
|
+
assist ask --title 'High-level review config' --body - < <scratch file>
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
- **Approved (exit 0)** — fold every printed inline comment into the answers (a comment on a glob edits or drops it; a comment on the scope switches it), then write.
|
|
45
|
+
- **Rejected (non-zero exit)** — write nothing. Address the reason and each comment, re-check any changed glob still matches files, revise the scratch file and re-run `assist ask`.
|
|
46
|
+
|
|
47
|
+
Outside a web session `assist ask` only prints the markdown and exits 0 without a decision: ask the user in chat instead, and write only once they have answered.
|
|
34
48
|
|
|
35
49
|
## Step 4: Write the answers
|
|
36
50
|
|