@staff0rd/assist 0.885.0 → 0.885.2

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
@@ -76,7 +76,7 @@ The user guide is a static site built from JSON pages in `docs/guide/pages/` and
76
76
  - `/restructure` - Analyze and restructure tightly-coupled files
77
77
  - `/review-config` - Configure this repo's high-level review checklist keys
78
78
  - `/review-ci` - Install a GitHub workflow that reviews new PRs with Claude and Codex through LiteLLM or Azure AI Foundry, without depending on assist
79
- - `/review-high-level [number]` - Open the high-level review checklist for the current branch's PR, or PR `<number>`, as a background task, answering diff questions while it is open
79
+ - `/review-high-level [number]` - Open the high-level review checklist for the current branch's PR, or PR `<number>`, as a background task, answering diff questions while it is open; outside a web session, show the printed checklist
80
80
  - `/review-pr-comments` - Process PR review comments one by one
81
81
  - `/jira [action] [KEY] [args]` - Jira actions: `view`, `associate`, `update`, `started`, `done`, `help`. `[KEY]` defaults to the session's backlog item's
82
82
  - `/github [action] [ref] [args]` - GitHub issue actions: `view`, `edit`, `create`, `associate`, `update`, `started`, `done`, `help`. `[ref]` defaults to the session's backlog item's; a bare `/github <ref>` runs `edit`
@@ -11,10 +11,13 @@ assist review --high-level $ARGUMENTS
11
11
 
12
12
  If this is a re-invocation in a session that already ran it, re-run it anyway — never assume the checklist is still open, since the pane may have gone even while a previous task still looks alive. Stop any still-running previous `assist review --high-level` background task first, then launch it afresh.
13
13
 
14
- Run it as a background task — it opens the checklist in the web UI preview pane and returns once the user approves or requests changes. Do not review the PR yourself or post anything to GitHub.
14
+ Run it as a background task. In an assist web session it opens the checklist in the web UI preview pane and returns once the user approves or requests changes; otherwise it prints the checklist and exits straight away. Do not review the PR yourself or post anything to GitHub.
15
15
 
16
- Once it is launched, say in one line that the checklist is open and end your turn straight away. Do not wait on the task — no polling its output, `sleep`, `Monitor` or reading its output file — and the "do no other work until it returns" rule for sign-off commands does not apply here. Input the user sends while you are mid-turn only queues behind it, so staying in the turn blocks every question until the review closes.
16
+ Once it is launched, say in one line that the high-level review has started and end your turn straight away. Do not say a pane is open — you only learn which case applies from the task's output. Do not wait on the task — no polling its output, `sleep`, `Monitor` or reading its output file — and the "do no other work until it returns" rule for sign-off commands does not apply here. Input the user sends while you are mid-turn only queues behind it, so staying in the turn blocks every question until the review closes.
17
17
 
18
18
  While it runs, the user may send diff comments from the pane: a file path and line range, the quoted code, and a note. Answer each one as its own turn in the terminal by reading the code and the PR's diff — explain, or say whether the concern holds — then end the turn again, leaving the review running. Do not edit files, post to GitHub or restart the review in reply. These answers live in the terminal only; nothing is added to the saved review.
19
19
 
20
- When the task's completion notification arrives, report the verdict and the path it saved the review to, quoting the command's own output. If the user left comments on any item, list them.
20
+ When the task's completion notification arrives, read its output:
21
+
22
+ - **Printed checklist** (it ends by suggesting running inside an assist session, and has no `Verdict:` line) — there was no preview pane. Show the user the printed checklist in full, and do not mention a pane.
23
+ - **Otherwise** — report the verdict and the path it saved the review to, quoting the command's own output. If the user left comments on any item, list them.