@staff0rd/assist 0.307.0 → 0.308.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 +1 -0
- package/claude/commands/bug.md +2 -0
- package/dist/commands/sessions/web/bundle.js +51 -51
- package/dist/index.js +455 -440
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -93,6 +93,7 @@ After installation, the `assist` command will be available globally. You can als
|
|
|
93
93
|
- `assist prs list-comments` - List all comments on the current branch's pull request
|
|
94
94
|
- `assist prs fixed <comment-id> <sha>` - Reply with commit link and resolve thread
|
|
95
95
|
- `assist prs wontfix <comment-id> <reason>` - Reply with reason and resolve thread
|
|
96
|
+
- `assist prs reply <comment-id> <body>` - Reply to a comment thread without resolving it
|
|
96
97
|
- `assist prs comment <path> <line> <body>` - Add a line comment to the pending review
|
|
97
98
|
- `assist review [number] [options]` - Run Claude and Codex in parallel to review the open PR for the current branch. The diff is fetched from GitHub (base SHA → head SHA via `gh pr diff`), so stale local base branches don't pollute the review; fails fast if no PR is open. By default, prompts before posting line-bound comments and then prompts again to submit the pending review (defaulting to no). Findings whose lines fall outside the diff are skipped with a warning rather than being silently dropped by GitHub. Cached `claude.md` / `codex.md` / `synthesis.md` are reused when present; if any reviewer is re-run, the synthesis is invalidated.
|
|
98
99
|
- `[number]` - Run `gh pr checkout <number>` first, then review that PR's branch. If the checkout fails (dirty working tree, unknown PR number), the review aborts
|
package/claude/commands/bug.md
CHANGED
|
@@ -17,6 +17,8 @@ Ask short, targeted questions one at a time to fill in any gaps. You need three
|
|
|
17
17
|
2. **Expected behavior** — what should happen?
|
|
18
18
|
3. **Actual behavior** — what happens instead?
|
|
19
19
|
|
|
20
|
+
Before asking the user about existing functionality — how a feature currently works, what a command does, where something lives — investigate the codebase first and answer it yourself. Only ask the user about things the code can't tell you (their intent, what they observed, how to reproduce it).
|
|
21
|
+
|
|
20
22
|
Skip questions the user has already answered. Stop asking as soon as you have enough to write a clear bug report — don't over-interrogate.
|
|
21
23
|
|
|
22
24
|
## Step 3: Propose the item
|