← ClaudeAtlas

wave-reviewerlisted

Use to understand or operate the wave reviewer — the second agent that checks one issue's finished work before a pull request is opened, and that only ever reads. It runs on every issue in the batch, however small the change, re-runs the project's own tests against the commit the batch started from, and answers with one of three verdicts: looks good, needs changes, or a question that has to be answered first. Triggers on "review this wave row", "what does the wave-reviewer check", "run the reviewer on <branch>".
formtrieb/flotilla · ★ 3 · Code & Development · score 69
Install: claude install-skill formtrieb/flotilla
# wave-reviewer The Wave Reviewer is the **agent** (`.claude/agents/wave-reviewer.md`) `wave-start` dispatches between every Worker-finish and PR-open. This skill is the operator's view of it: when it runs, what a sound verdict rests on, and the boundary it must not cross. The check mechanics live in [reference/reviewer-checks.md](reference/reviewer-checks.md); the schema-validated return contract is the agent definition itself. ## When it runs - Automatically, per row, inside the `wave-start` Workflow script (`agent({ agentType: 'wave-reviewer', schema: REVIEWER_VERDICT_SCHEMA })`). - **Universal dispatch** — every row, regardless of Risk. Risk is reported (and routed on downstream), never a gate on whether the Reviewer runs (ADR-0016: the reviewer is uniform — there is no per-Risk brief profile, unlike the Ur). - You rarely invoke it by hand. Reach for this skill to understand a verdict, or to run the same checks manually on a stuck branch. ## What a sound verdict rests on - **Re-verification, not re-reading.** Worker-report drift is the #1 failure mode. Every "green/met/clean" claim comes from a command run in this dispatch. - **The wave-anchor SHA as the diff base — never `main`.** Diffing against `main` surfaces the whole feature delta and hides the Worker's actual change. The anchor SHA is the wave's base; the Worker `git reset --hard`-ed to it. - **A stable named ref for the branch under review, confirmed before use — never `FETCH_HEAD`.** `FETCH_HEAD` is a single