wave-reviewerlisted

# 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: REVIEWER_AGENT, schema: REVIEWER_VERDICT_SCHEMA })`) — `REVIEWER_AGENT` is never spelled by hand. It is the compose-time constant the engine's `compose-driver` derives for the form this wave is actually running in: the bare agent-definition name in source form, `<plugin>:<agent>` once installed, or the `--reviewer-agent` override when the Coordinator names it outright. - **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 d