@staff0rd/assist 0.77.0 → 0.79.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/README.md CHANGED
@@ -31,6 +31,7 @@ After installation, the `assist` command will be available globally.
31
31
 
32
32
  ## Claude Commands
33
33
 
34
+ - `/comment` - Add pending review comments to the current PR
34
35
  - `/commit` - Commit only relevant files from the session
35
36
  - `/devlog` - Generate devlog entry for the next unversioned day
36
37
  - `/next-backlog-item` - Pick and implement the next backlog item
@@ -54,10 +55,11 @@ After installation, the `assist` command will be available globally.
54
55
  - `assist prs list-comments` - List all comments on the current branch's pull request
55
56
  - `assist prs fixed <comment-id> <sha>` - Reply with commit link and resolve thread
56
57
  - `assist prs wontfix <comment-id> <reason>` - Reply with reason and resolve thread
58
+ - `assist prs comment <path> <line> <body>` - Add a line comment to the pending review
57
59
  - `assist backlog` - Start the backlog web UI (same as `backlog web`)
58
60
  - `assist backlog init` - Create an empty assist.backlog.yml
59
61
  - `assist backlog list [--status <type>] [-v]` - List all backlog items with status icons
60
- - `assist backlog add` - Add a new backlog item interactively
62
+ - `assist backlog add` - Add a new backlog item interactively (prompts for type: story/bug)
61
63
  - `assist backlog start <id>` - Set a backlog item to in-progress
62
64
  - `assist backlog done <id>` - Set a backlog item to done
63
65
  - `assist backlog delete <id>` - Delete a backlog item
@@ -0,0 +1,39 @@
1
+ ---
2
+ description: Add pending review comments to the current PR
3
+ allowed_args: "<item numbers, e.g. 1,2,3>"
4
+ ---
5
+
6
+ Add pending review comments to the current branch's pull request for the specified items.
7
+
8
+ ## Parsing Arguments
9
+
10
+ Parse `$ARGUMENTS` as a comma-separated list of item numbers (e.g. `1,2` or `1,2,3`). These refer to items in a numbered list from earlier in the conversation.
11
+
12
+ ## Finding the Referenced List
13
+
14
+ Look back through the conversation for the most recent numbered list of issues, suggestions, or comments. Each item should have enough context to determine:
15
+ - **path**: the file path
16
+ - **line**: the line number
17
+ - **body**: a concise comment describing the issue
18
+
19
+ If any referenced item number doesn't exist in the list, report the error and skip it.
20
+
21
+ ## Posting Comments
22
+
23
+ For each referenced item, run:
24
+
25
+ ```
26
+ assist prs comment <path> <line> '<body>' 2>&1
27
+ ```
28
+
29
+ **Important:** Always use single quotes around `<body>`, never double quotes. Double quotes cause shell escaping issues with backticks and special characters.
30
+
31
+ The body must:
32
+ - Be a clear, concise description of the issue (1-2 sentences)
33
+ - Not contain "claude" or "opus" (case-insensitive) — the command will reject it
34
+ - Not contain single quotes (reword to avoid them)
35
+ - Use backticks to wrap inline code or keywords (e.g. `functionName`)
36
+
37
+ ## Report
38
+
39
+ After posting, summarise which comments were added and any that failed.