You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,12 @@ All notable changes to the claude-plugins project will be documented in this fil
4
4
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Entries are listed newest-first; each plugin section is treated as released when merged to `main`.
6
6
7
+
### code-review v3.4.0
8
+
9
+
#### Changed
10
+
- The `/code-review` orchestrator now runs the deterministic review prefix via the `run-prefix` helper loop instead of walking those stages one at a time. After session setup it invokes `run-prefix` and acts on the returned status: dispatching a signal-extraction or coverage-critic agent and resuming when one is needed, presenting hygiene findings and exiting on a hygiene-only run, or — once the whole prefix (including model routing and partitioning) is done — printing the cache/fast-path notices and handing off to the reviewer fleet. This collapses roughly nineteen helper stages and their serial model turns into a handful of orchestrator turns, the single biggest turn-count reduction in a review. The per-stage walk remains fully documented as the labeled fallback, used only when `run-prefix` reports an error or is unavailable (e.g. an older plugin cache), so no behavior is lost.
11
+
- The stage-by-stage "Walker Contract" is now scoped to the reviewer/verification/presentation tail (spawn-reviewers onward) plus that prefix fallback; the hygiene-only exit and the routing/partition gate are performed inside `run-prefix` and surfaced through its result. The single-agent dispatch skill and `SCHEMA.md` were updated to match (the skill returns control for `run-prefix` to resume in the default flow, and `SCHEMA.md` documents the routing-failure recovery anchor and the shallow-tier spawn-spec stage).
(default cap=20, BHA floor=1 waived for docs-only PRs, required overflow
57
57
fails closed and emits coverage gaps).
58
58
-**`prepare-run`** emits a declarative `run_plan.json` describing the 30-stage
59
-
pipeline. (The orchestrator rewrite over this plan is a follow-up.)
59
+
pipeline; the orchestrator runs its deterministic prefix in one process via
60
+
`run-prefix` and walks the reviewer/verification/presentation tail
61
+
stage-by-stage (PLN-1229).
60
62
-**Canonical `prompt_hash`** folds in `schema_version`: a MAJOR schema bump
61
63
invalidates every cache namespace at once.
62
64
@@ -66,7 +68,7 @@ The terminal artifact of every review run is `review_result.json` (PLN-722 envel
66
68
67
69
| Component | Role |
68
70
|---|---|
69
-
|`start.md`| Orchestrator command. Parses flags, sets up the session, invokes the helper CLI subcommands in sequence, spawns reviewer sub-agents, collects results, and presents findings |
71
+
|`start.md`| Orchestrator command. Parses flags, sets up the session, runs the deterministic prefix in one process via `run-prefix` (then walks the reviewer tail stage-by-stage), spawns reviewer sub-agents, collects results, and presents findings |
70
72
|`github-review.md`| Loaded by the orchestrator only in GitHub mode. Contains PR metadata resolution, file-based handoff format for CI, and summary format |
71
73
|`code_review_helpers.py`| Python CLI that handles all deterministic work: git diff parsing, hygiene pattern matching, file partitioning, risk scoring/model routing, finding validation, cache management, and GitHub comment posting |
72
74
|`shared_prompt.txt`| Constraints injected into every reviewer agent prompt: file assignment rules, evidence standards, severity definitions, and output format |
@@ -196,7 +198,7 @@ The orchestrator executes these steps in order:
196
198
13.**Review state write** — persists the current diff tip so future `--since-last-review` runs can narrow the scope
197
199
14.**Footer** — prints elapsed time, token usage stats, and writes the deterministic verdict JSON to `<CR_DIR>/verdict.json` (consumed by the `code` plugin's `run-loop.sh`)
198
200
199
-
(Step numbers in this list are illustrative; the canonical 30-stage ordering lives in `prepare-run`'s `run_plan.json`.)
201
+
(Step numbers in this list are illustrative; the canonical 30-stage ordering lives in `prepare-run`'s `run_plan.json`. Steps 2–8 — the deterministic prefix through routing and partitioning — run in a single process via the `run-prefix` helper; the orchestrator walks the reviewer/validation/presentation tail from step 9 onward.)
0 commit comments