review

review — Universal Review Gate

Runtime syntax: invoke the plugin copy through the active runtime's owner-qualified skill selector; use a bare selector only when intentionally selecting a user-tier copy (a separately installed personal copy; Genie no longer seeds this tier). Cross-skill prose below uses bare names as portable semantic routes; the orchestrator resolves the selector for the active runtime.

Validate a design, wish plan, completed execution, or PR against its governing criteria. Dispatch as a subagent — never review your own work inline. The deliverable is findings plus a verdict: report and stop — never implement fixes, however small.

Context Injection

When spawned as a reviewer subagent, your dispatch prompt carries the curated scope: the target (DESIGN.md, wish draft, completed work, or PR diff), its exact path, and the extracted design or acceptance criteria. A design review does not require a wish path; later pipelines include .genie/wishes/<slug>/WISH.md. Use the supplied context directly — do not re-parse information already provided.

When to Use

• After brainstorm — validate DESIGN.md before converting it into a wish
• Before work — validate a wish plan is ready for execution
• After work — verify implementation meets acceptance criteria
• Before merge — check a PR diff against wish scope

Flow

1. Detect target — DESIGN.md, wish draft, completed work, or PR diff.
2. Select pipeline — the matching checklist below.
3. Run checklist — evaluate each criterion, collecting evidence.
4. Run validations — execute validation commands; capture pass/fail output and confirm their scope is proportional to the diff's risk and reach. Documentation-only changes, including deterministic generated documentation or plugin skill mirrors, use relevant format, link, example, generator, parity, or content-contract checks; runtime changes use focused behavior tests and add type, lint, or build checks for boundaries reached. Shared runtime/core behavior, dependency or lockfile, generated executable or runtime artifact, configuration or schema, CI or release, broad-refactor, or uncertain-impact changes require the repository full gate plus affected build or end-to-end checks. Reject zero validation and under-validation. A passing full-suite run is always valid evidence; a missing scope rationale is at most a MEDIUM gap, never by itself grounds for FIX-FIRST. A repository-documented gate is by itself sufficient justification for its scope. Preserve required aggregate integration and release gates.
5. Tag gaps — classify every unmet criterion by severity.
6. Return verdict — SHIP, FIX-FIRST, or BLOCKED, with exact fixes (files, commands, what to change) for each gap.