@staff0rd/assist 0.1121.2 → 0.1123.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 → agent}/commands/add-rule.md +12 -6
- package/dist/built-version +1 -1
- package/dist/commands/sessions/web/bundle.js +409 -409
- package/dist/index.js +198 -152
- package/package.json +2 -1
- /package/{claude → agent}/commands/add-command.md +0 -0
- /package/{claude → agent}/commands/ask.md +0 -0
- /package/{claude → agent}/commands/branch.md +0 -0
- /package/{claude → agent}/commands/bug.md +0 -0
- /package/{claude → agent}/commands/close.md +0 -0
- /package/{claude → agent}/commands/comment.md +0 -0
- /package/{claude → agent}/commands/commit.md +0 -0
- /package/{claude → agent}/commands/design.md +0 -0
- /package/{claude → agent}/commands/devlog.md +0 -0
- /package/{claude → agent}/commands/draft.md +0 -0
- /package/{claude → agent}/commands/extension.md +0 -0
- /package/{claude → agent}/commands/fix-conflict.md +0 -0
- /package/{claude → agent}/commands/fix-rules.md +0 -0
- /package/{claude → agent}/commands/forward-comments.md +0 -0
- /package/{claude → agent}/commands/github.md +0 -0
- /package/{claude → agent}/commands/inspect.md +0 -0
- /package/{claude → agent}/commands/jira.md +0 -0
- /package/{claude → agent}/commands/miro.md +0 -0
- /package/{claude → agent}/commands/next.md +0 -0
- /package/{claude → agent}/commands/pr.md +0 -0
- /package/{claude → agent}/commands/prompts.md +0 -0
- /package/{claude → agent}/commands/prs-slack.md +0 -0
- /package/{claude → agent}/commands/prs-status.md +0 -0
- /package/{claude → agent}/commands/raven.md +0 -0
- /package/{claude → agent}/commands/refactor.md +0 -0
- /package/{claude → agent}/commands/refine.md +0 -0
- /package/{claude → agent}/commands/releases-configure.md +0 -0
- /package/{claude → agent}/commands/rename.md +0 -0
- /package/{claude → agent}/commands/restructure.md +0 -0
- /package/{claude → agent}/commands/review-config.md +0 -0
- /package/{claude → agent}/commands/review-high-level.md +0 -0
- /package/{claude → agent}/commands/review-pr-comments.md +0 -0
- /package/{claude → agent}/commands/run-logs.md +0 -0
- /package/{claude → agent}/commands/screenshot.md +0 -0
- /package/{claude → agent}/commands/seq.md +0 -0
- /package/{claude → agent}/commands/show.md +0 -0
- /package/{claude → agent}/commands/slack-post.md +0 -0
- /package/{claude → agent}/commands/sql.md +0 -0
- /package/{claude → agent}/commands/supabase.md +0 -0
- /package/{claude → agent}/commands/sync.md +0 -0
- /package/{claude → agent}/commands/test-cover.md +0 -0
- /package/{claude → agent}/commands/test-review.md +0 -0
- /package/{claude → agent}/commands/transcripts.md +0 -0
- /package/{claude → agent}/commands/verify-new.md +0 -0
- /package/{claude → agent}/commands/verify.md +0 -0
- /package/{claude → agent}/design-system-prompt.md +0 -0
- /package/{claude → agent}/skills/accessibility-audit.md +0 -0
- /package/{claude → agent}/skills/ai-slop-check.md +0 -0
- /package/{claude → agent}/skills/component-extract.md +0 -0
- /package/{claude → agent}/skills/design-system-extract.md +0 -0
- /package/{claude → agent}/skills/discovery-questions.md +0 -0
- /package/{claude → agent}/skills/frontend-aesthetic-direction.md +0 -0
- /package/{claude → agent}/skills/generate-variations.md +0 -0
- /package/{claude → agent}/skills/hierarchy-rhythm-review.md +0 -0
- /package/{claude → agent}/skills/interaction-states-pass.md +0 -0
- /package/{claude → agent}/skills/make-a-deck.md +0 -0
- /package/{claude → agent}/skills/make-a-prototype.md +0 -0
- /package/{claude → agent}/skills/make-tweakable.md +0 -0
- /package/{claude → agent}/skills/polish-pass.md +0 -0
- /package/{claude → agent}/skills/wireframe.md +0 -0
|
@@ -1,17 +1,18 @@
|
|
|
1
1
|
---
|
|
2
2
|
description: Capture a new CLAUDE.md rule from a review comment
|
|
3
|
-
allowed_args: "[quoted text, file and note from the comment pane]"
|
|
3
|
+
allowed_args: "[quoted text, file and note from the comment pane] [--repo [name] | --user | --node]"
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
You are turning a review comment into a written rule in a `CLAUDE.md` file, so the same mistake is caught next time. `$ARGUMENTS` carries what the comment pane sent: an optional `File:` line, the quoted text in a fenced block, and the reviewer's note.
|
|
7
7
|
|
|
8
8
|
## Step 1: Read what you were given
|
|
9
9
|
|
|
10
|
-
Pull
|
|
10
|
+
Pull these out of `$ARGUMENTS`:
|
|
11
11
|
|
|
12
12
|
- **File** — the path the selection came from, if a `File:` line is present. The document preview pane has no path, so it may be missing.
|
|
13
13
|
- **Quote** — the selected text, the concrete example of the rule being broken.
|
|
14
14
|
- **Note** — the reviewer's words, the substance of the rule.
|
|
15
|
+
- **Scope flag** — a `--repo` (optionally followed by a repo name), `--user` or `--node` in the arguments. It is an instruction about where the rule goes, not part of the note: strip it from the note before wording the rule.
|
|
15
16
|
|
|
16
17
|
If `$ARGUMENTS` is empty, ask the user what rule they want to add and skip to Step 3.
|
|
17
18
|
|
|
@@ -25,9 +26,14 @@ Ask the user a clarifying question only when the note is genuinely too vague to
|
|
|
25
26
|
|
|
26
27
|
## Step 3: Work out the scope
|
|
27
28
|
|
|
28
|
-
The scope is the directory whose `CLAUDE.md` gets the rule, or `
|
|
29
|
+
The scope is the directory whose `CLAUDE.md` gets the rule, or `advice.rules` in `repo (db)`, `user (db)` or `user (node)`.
|
|
30
|
+
|
|
31
|
+
If Step 1 found a scope flag, it fixes the scope: `--repo [name]` is `repo (db)` (for the named repo when one follows), `--user` is `user (db)`, `--node` is `user (node)`. Use it as given — do not infer a different scope or second-guess it — and go to Step 4.
|
|
32
|
+
|
|
33
|
+
Otherwise infer it — do not ask by default:
|
|
29
34
|
|
|
30
35
|
- If the rule is about agent conduct that holds in every repo rather than about this repo's code or docs (e.g. "give the URL, not a nav path", "don't ask for sign-off in chat"), the scope is **`user (db)`**: it goes to `advice.rules` in the shared db and reaches every session in every repo on every node. A rule that only makes sense for this repo's files, conventions or tooling never goes there. Use `user (node)` (this node's `~/.assist.yml`) only when the user asks for the rule to stay on this node.
|
|
36
|
+
- If the rule is about agent conduct specific to this repo (how to work in it, its tooling or workflow) and should reach every node working on it, but is not a convention about the repo's code or docs that belongs in a checked-in `CLAUDE.md`, the scope is **`repo (db)`**: it goes to `advice.rules` in the shared per-repo override that every node sees for this repo.
|
|
31
37
|
- With a file path, the default is the nearest `CLAUDE.md` walking up from that file's directory to the repo root. `assist rules list <path>` shows what is already in scope there, which tells you where sibling rules live.
|
|
32
38
|
- If the note is clearly about a kind of document that lives in one directory (and the file sits in it), that directory's `CLAUDE.md` is the scope — pass `--scope <dir>/CLAUDE.md` to create it there when it does not exist yet.
|
|
33
39
|
- If the rule plainly applies repo-wide, use the root `CLAUDE.md`.
|
|
@@ -49,14 +55,14 @@ For a `user (db)` rule, pass `--user` instead of `--scope` (the two can't be com
|
|
|
49
55
|
assist rules add '<rule text>' --title '<title>' --user 2>&1
|
|
50
56
|
```
|
|
51
57
|
|
|
52
|
-
It appends the rule to `advice.rules` in `user (db)` with no R-code. For `user (node)`, pass `--node` instead of `--user`.
|
|
58
|
+
It appends the rule to `advice.rules` in `user (db)` with no R-code. For `user (node)`, pass `--node` instead of `--user`. For `repo (db)`, pass `--repo` (or `--repo <name>` when the flag named a repo) instead; it appends to `advice.rules` in that repo's `repo (db)` block.
|
|
53
59
|
|
|
54
60
|
Use single quotes around the rule text to avoid shell escaping issues.
|
|
55
61
|
|
|
56
|
-
Show the command output — it names the allocated code (or, for
|
|
62
|
+
Show the command output — it names the allocated code (or, for an `advice.rules` rule, the title) and where it went — then tell the user in one line which rule was added and where.
|
|
57
63
|
|
|
58
64
|
## Step 5: Fix what broke it
|
|
59
65
|
|
|
60
|
-
The rule exists because something broke it, so the quoted text is now a live violation. Rectify it in the same pass, without being asked: edit the quoted text in the file the `File:` line named, so it follows the rule you just wrote. Where there was no `File:` line, fix the draft or the text the quote came from.
|
|
66
|
+
The rule exists because something broke it, so the quoted text is now a live violation. Rectify it in the same pass, without being asked: edit the quoted text in the file the `File:` line named, so it follows the rule you just wrote. Where there was no `File:` line, fix the draft or the text the quote came from. An `advice.rules` rule (`repo (db)`, `user (db)` or `user (node)`) is no exception: the quoted violation still gets fixed, even though the rule went to `advice.rules` rather than a file in this repo.
|
|
61
67
|
|
|
62
68
|
Fix the instance you were given. Do not sweep the rest of the repo for other violations of the new rule unless the user asks for that.
|
package/dist/built-version
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
0.
|
|
1
|
+
0.1123.0
|