@staff0rd/assist 0.809.0 → 0.811.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/commands/github.md +2 -0
- package/claude/skills/review-ci/scripts/review.mjs +1 -1
- package/dist/commands/sessions/web/bundle.js +354 -354
- package/dist/index.js +1108 -1022
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -148,7 +148,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
|
|
|
148
148
|
- `review.highLevel.testPaths` - Globs of test files whose changed tests back the tests checklist item as a file > describe > it hierarchy, each test's source a click away and each open to its own comment; defaults to `**/*.{test,spec}.{ts,tsx,js,jsx}`
|
|
149
149
|
- `assist github commits <org> [--since <date>] [--top <n>] [--json]` - Report commit activity across a GitHub organisation
|
|
150
150
|
- `assist github issue create --title <title> --body <body> [-R <owner>/<repo>] [--type <name>] [--parent <issue>] [--project <number>] [--status <name>] [--label <name>]` - Create a GitHub issue on the current repo (or `-R`'s), previewed for approval in a web session; the options set its issue type, parent issue, project, project status and labels
|
|
151
|
-
- `assist github issue edit <number> [-R <owner>/<repo>] [--body <body>] [--fresh] [--parent <issue>]` - Rework an issue's body in the web preview pane; `--body` previews a proposed body (`-` reads stdin) instead of the current one, `--fresh` discards an unpushed revision, and `--parent` instead makes the issue a sub-issue of `<issue>`
|
|
151
|
+
- `assist github issue edit <number> [-R <owner>/<repo>] [--body <body>] [--fresh] [--fetch] [--parent <issue>]` - Rework an issue's body in the web preview pane; `--body` previews a proposed body (`-` reads stdin) instead of the current one, `--fetch` writes the current body to the working file without previewing so it can be edited before the first preview, `--fresh` discards an unpushed revision, and `--parent` instead makes the issue a sub-issue of `<issue>`
|
|
152
152
|
- `assist github issue comment <number> --body <body> [-R <owner>/<repo>]` - Comment on a GitHub issue, previewed for approval in a web session; `--body -` reads stdin
|
|
153
153
|
- `assist github issue edit-comment <comment-id> --body <body> [-R <owner>/<repo>]` - Replace the body of a posted issue comment, previewed for approval in a web session; `--body -` reads stdin
|
|
154
154
|
- `assist github issue started <number> [-R <owner>/<repo>]` - Assign a GitHub issue to yourself and move it to In Progress on its project boards
|
|
@@ -231,7 +231,7 @@ The Config tab of the sessions web dashboard never shows secret values; their fi
|
|
|
231
231
|
|
|
232
232
|
### Verify and lint
|
|
233
233
|
|
|
234
|
-
- `assist verify` - Run all verify:\* commands in parallel (from assist.yml run configs and package.json scripts)
|
|
234
|
+
- `assist verify` - Run all verify:\* commands in parallel (from assist.yml run configs and package.json scripts); with `verify.roots`, each listed package dir's `verify:*` scripts run as `<root>:verify:*` when files under it change, and the repo-root package.json scripts run only for changes outside every root
|
|
235
235
|
- `assist verify all` - Run all checks, ignoring diff-based filters
|
|
236
236
|
- `assist verify --measure` - Run all verify:\* commands and time each one
|
|
237
237
|
- `assist verify init [--package-json]` - Add verify scripts to a project
|
|
@@ -53,6 +53,8 @@ assist github issue edit <number> -R <owner>/<repo> 2>&1
|
|
|
53
53
|
|
|
54
54
|
If you already know the body you want (e.g. the user asked for a specific rewrite), read the current body with `gh issue view`, compose the revision, and pass it with `--body -` on stdin so the first preview shows your proposal rather than the unchanged body.
|
|
55
55
|
|
|
56
|
+
For a targeted change to the current body (strike items out, tick a box), run `assist github issue edit <number> -R <owner>/<repo> --fetch` first: it writes the current body to the working file and prints its path without opening a preview. Edit that file in place, then run the command without `--fetch` so the first preview shows your revision. Never run it without `--fetch` just to get the body.
|
|
57
|
+
|
|
56
58
|
Do not check for a web session yourself — the command already knows. In a web session it fetches the issue's current body, opens it in the preview pane, and pushes the pane's markdown back on approval; outside one it just prints the issue. Only the body is ever touched — the title, labels, assignees and state are left alone.
|
|
57
59
|
|
|
58
60
|
Display the output so the user can see what happened. If the command exits non-zero, relay what it reported and stop — nothing was pushed. Two cases to relay verbatim:
|