@staff0rd/assist 0.251.0 → 0.253.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 +2 -2
- package/claude/CLAUDE.md +3 -0
- package/dist/commands/sessions/web/bundle.js +58 -58
- package/dist/index.js +13 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -252,8 +252,8 @@ Web sessions are owned by a long-lived daemon process, not the web server: the s
|
|
|
252
252
|
|
|
253
253
|
When iterating on assist itself: web server changes only need the `assist sessions` process restarted — sessions survive. Daemon/session-core changes need `assist daemon restart` to load the new code; this kills the PTYs, then claude sessions — including assist sessions that wrap claude, like `assist draft` — are auto-respawned via `claude --resume` with scrollback starting fresh, while run sessions (and assist sessions whose claude sessionId was never discovered) reappear as not-restored tiles that can be retried.
|
|
254
254
|
- `assist next [id] [--once]` - Alias for `backlog next [id]`; `--once` exits after the first completed item run instead of prompting for another
|
|
255
|
-
- `assist draft [--once]` (alias: `feat`) - Launch Claude in `/draft` mode, chain into next on `/next` signal; `--once` exits when the done signal arrives after the initial draft completes
|
|
256
|
-
- `assist bug [--once]` - Launch Claude in `/bug` mode, chain into next on `/next` signal; `--once` exits when the done signal arrives after the initial bug report completes
|
|
255
|
+
- `assist draft [description] [--once]` (alias: `feat`) - Launch Claude in `/draft` mode, chain into next on `/next` signal; an optional `description` is forwarded as `/draft <description>`; `--once` exits when the done signal arrives after the initial draft completes
|
|
256
|
+
- `assist bug [description] [--once]` - Launch Claude in `/bug` mode, chain into next on `/next` signal; an optional `description` is forwarded as `/bug <description>`; `--once` exits when the done signal arrives after the initial bug report completes
|
|
257
257
|
- `assist refine [id] [--once]` - Launch Claude in `/refine` mode to refine a backlog item; prompts for selection when no id given; `--once` exits when the done signal arrives after refinement completes
|
|
258
258
|
- `assist review-comments [number]` - Launch Claude in `/review-comments` mode to process PR review comments (single session, no chaining); when a PR number is supplied, checks out that PR via `gh pr checkout` first
|
|
259
259
|
- `assist signal next [id]` - Write a next signal to chain into `assist next`; when `id` is supplied, the parent launcher runs that backlog item directly
|
package/claude/CLAUDE.md
CHANGED
|
@@ -17,3 +17,6 @@ When the user mentions a Jira issue key (e.g. `BAD-671`, `PROJ-123`), use the At
|
|
|
17
17
|
|
|
18
18
|
## Commenting code
|
|
19
19
|
Do not include comments for standard logic or syntax. Only comment if the specific line involves unintuitive complexity or a hack.
|
|
20
|
+
|
|
21
|
+
## Backlog items, PRs, and commits
|
|
22
|
+
Do not mention assist backlog items in PR descriptions or PR comments. The reference goes the other way: mention the relevant commits or PRs in the assist backlog item.
|