@staff0rd/assist 0.663.0 → 0.665.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 CHANGED
@@ -55,6 +55,7 @@ After installation, the `assist` command will be available globally. You can als
55
55
  - `/handover` - Write a session handover note for the next conversation
56
56
  - `/pr` - Raise a PR with a concise description, then watch CI in the background
57
57
  - `/prs-slack <number> [--no-confirm]` - Post a PR's title and URL to the Slack channel configured in `prs.slack`; `--no-confirm` skips the confirmation and posts straight away (used by chained announces)
58
+ - `/prs-status <owner/repo>...` - Run `assist prs status <repos> --json` over the named repos and write a markdown overview of what is still pending merge, sorting each open PR into pending review, changes requested, failing checks, ready to merge or drafts, re-listing anything untouched for 7+ days as stale, and naming any repo that could not be read. Writes to chat only — it creates no files and posts nowhere
58
59
  - `/refactor` - Run refactoring checks for code quality
59
60
  - `/prompts` - Analyze denied tool calls and suggest settings changes to auto-allow recurring prompts
60
61
  - `/recall` - Recall the most recent handover note for this repo
@@ -138,7 +139,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
138
139
  - `--apply` - Skip posting; walk through each finding asking apply/skip. Applied findings are fixed in the working tree
139
140
  - `--backlog` - Skip posting; file all findings as a single bug backlog item with one phase per finding
140
141
  - `--checkout-only` - Skip the review entirely; check the PR out and leave an idle interactive Claude session running in the checkout tree. Requires a PR number, and cannot be combined with `--refine`, `--apply`, `--backlog` or `--submit`
141
- - `--high-level` - Skip the LLM review; evaluate the high-level review checklist against the PR description and its changed files and print every item as pass, fail or manual. The deterministic items are What/Why present, description under `review.highLevel.descriptionWordCap`, a GitHub issue linked, and a screenshot or video whenever a changed file matches `review.highLevel.uiPaths`; the manual items — change structure, critical-file diffs, backend PR linked — are named with what backs them. Nothing is posted to GitHub. Cannot be combined with `--refine`, `--apply`, `--backlog`, `--submit` or `--checkout-only`. See [docs/high-level-review.md](docs/high-level-review.md)
142
+ - `--high-level` - Skip the LLM review; check the PR branch out and step through the high-level review checklist in the web UI preview pane, ticking the manual items and commenting on any item. The deterministic items are What/Why present, description under `review.highLevel.descriptionWordCap`, a GitHub issue linked, and a screenshot or video whenever a changed file matches `review.highLevel.uiPaths`; the manual items are change structure, critical-file diffs and backend PR linked. Approving or requesting changes writes the verdict, per-item state and comments to `~/.assist/high-level-reviews/<repo>/<branch>-<head-sha>.json` and prints the path. Outside an assist session the checklist is printed to the terminal instead. Nothing is posted to GitHub. Cannot be combined with `--refine`, `--apply`, `--backlog`, `--submit` or `--checkout-only`. See [docs/high-level-review.md](docs/high-level-review.md)
142
143
  - `--address-comments` - After the review posts comments and submits, start an Address Comments session (`assist review-pr-comments <n>`) for the PR. Only fires inside an assist session, and only when at least one comment was posted and the review was submitted
143
144
  - `--announce` - Announce the PR in Slack (`/prs-slack <n> --no-confirm`) at the tail of the chain: the Address Comments session announces once every thread is processed when one was started, otherwise a `/prs-slack` session is started directly. Announces exactly once, and only inside an assist session
144
145
  - `--verbose` - Per-line log output instead of the stacked-spinner UI (automatic in CI)
@@ -0,0 +1,77 @@
1
+ ---
2
+ description: Write a markdown overview of the open PRs across the named repos
3
+ allowed_args: "<owner/repo>..."
4
+ ---
5
+
6
+ Report what is still pending merge across the repos in `$ARGUMENTS`.
7
+
8
+ ## Step 1: Resolve the repos
9
+
10
+ `$ARGUMENTS` is one or more `owner/repo` arguments. With none, ask the user which repos to report on and stop — do not guess, and do not fall back to the current repo.
11
+
12
+ ## Step 2: Collect the facts
13
+
14
+ Run:
15
+
16
+ ```bash
17
+ assist prs status <repos> --json
18
+ ```
19
+
20
+ The payload is `{ repos: [{ repo, pullRequests: [...] }], errors: [{ repo, error }] }`. Each pull request carries `number`, `title`, `url`, `author`, `isBot`, `isDraft`, `createdAt`, `updatedAt`, `age` (a label like `3d`, derived from `updatedAt`), `ageHours`, `reviewDecision`, `reviews` (per-reviewer `state`), `checks.failing`, `checks.pending`, `mergeable`, and `unresolvedThreads`.
21
+
22
+ Use only what the payload says. `unresolvedThreads: null` means that PR's thread query failed — report it as unknown, never as zero. `ageHours: null` means the timestamp could not be parsed.
23
+
24
+ ## Step 3: Sort each PR into one bucket
25
+
26
+ Every non-draft PR belongs in exactly one section, taking the first that matches:
27
+
28
+ 1. **Pending review** — no failing checks, `mergeable` is not `CONFLICTING`, no unresolved threads, and `reviewDecision` is `REVIEW_REQUIRED` or absent with no approval in `reviews`.
29
+ 2. **Changes requested** — `reviewDecision` is `CHANGES_REQUESTED`, or `unresolvedThreads` is above zero.
30
+ 3. **Failing checks** — `checks.failing` is non-empty or `mergeable` is `CONFLICTING`.
31
+ 4. **Ready to merge** — `reviewDecision` is `APPROVED` with clean checks and no unresolved threads.
32
+
33
+ Drafts go in their own section regardless of the above.
34
+
35
+ ## Step 4: Write the overview
36
+
37
+ Write the overview to chat as markdown. Do not create files, and do not post anywhere.
38
+
39
+ ```markdown
40
+ # Open PRs — <repo>, <repo>
41
+
42
+ <n> open across <n> repos: <n> pending review, <n> changes requested, <n> failing checks, <n> ready to merge, <n> drafts.
43
+
44
+ ## Pending review
45
+
46
+ - [owner/repo#123](url) — Title (author, updated 3d ago)
47
+ - awaiting: alice (COMMENTED)
48
+
49
+ ## Changes requested
50
+
51
+ - [owner/repo#124](url) — Title (author, updated 6h ago)
52
+ - 2 unresolved comments, bob requested changes
53
+
54
+ ## Failing checks
55
+
56
+ - [owner/repo#125](url) — Title (author, updated 2d ago)
57
+ - failing: build, lint
58
+ - conflicting with the base branch
59
+
60
+ ## Ready to merge
61
+
62
+ - [owner/repo#126](url) — Title (author, updated 1d ago)
63
+
64
+ ## Drafts
65
+
66
+ - [owner/repo#127](url) — Title (author, updated 9d ago)
67
+
68
+ ## Stale — no activity in 7+ days
69
+
70
+ - [owner/repo#127](url) — 9d
71
+
72
+ ## Could not be read
73
+
74
+ - owner/repo — <error>
75
+ ```
76
+
77
+ Omit any section with nothing in it. The stale section re-lists any PR whose `ageHours` is 168 or more, whichever bucket it sits in; mark bot-authored PRs with `[bot]` after the title. Include the "Could not be read" section whenever `errors` is non-empty, even if every other repo succeeded. When there are no open PRs at all, say so in one line instead of emitting empty sections.