Review-code

Validate a single implementation report produced by an implementation skill. The skill reads the report, the plan it references, and the actual git commits, then renders a verdict per acceptance criterion plus cross-cutting findings. Output is a review report on disk; no code changes.

Inputs and outputs

• Plan input: <cwd>/.plans/<feature>/plan.md.
• Report input: <cwd>/.plans/<feature>/implementations/{with-design,code}/{feat,fix,refactor}/<phase_number>.md produced by an implementation skill. The with-design vs code subdirectory marks whether the phase was UI or non-UI — UI checks run only against with-design reports.
• Code input: the git history. Every AC in the report cites at least one commit SHA (default mode) or 2–3 SHAs (TDD mode: [red], [green], optional refactor). Read each commit's diff with git show <sha> and inspect changed files in their post-commit state.
• Review output: <cwd>/.plans/<feature>/reviews/{with-design,code}/<phase_number>.md — verdict per AC, cross-cutting issues, recommended follow-ups. Mirrors the implementation report's directory variant so a single phase has paired implementation + review artefacts.

Mandatory preconditions

Run before writing any verdict, in this order: