@staff0rd/assist 0.804.0 → 0.806.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 -1
- package/claude/commands/github.md +2 -0
- package/dist/commands/sessions/web/bundle.js +409 -409
- package/dist/index.js +12 -8
- 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>] [--fresh] [--parent <issue>]` - Rework an issue's body in the web preview pane; `--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] [--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>`
|
|
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
|
|
@@ -51,6 +51,8 @@ Rework the issue's body in the assist web preview pane. This is what a bare issu
|
|
|
51
51
|
assist github issue edit <number> -R <owner>/<repo> 2>&1
|
|
52
52
|
```
|
|
53
53
|
|
|
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
|
+
|
|
54
56
|
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.
|
|
55
57
|
|
|
56
58
|
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:
|