Code Review

Overview

Perform a rigorous, adversarial review that cross-checks story claims and acceptance criteria against the real code changes. Prioritize concrete, reproducible findings with file and line references. If the code is clean, explicitly say so.

Quick Start

• Determine scope: story file + repository, or a diff/PR.
• Identify repo root (use git) and collect changed files via git status --porcelain, git diff --name-only, and git diff --cached --name-only.
• Load story/spec inputs if provided; otherwise ask for the story/spec or acceptance criteria.
• Exclude non-application files and folders (.cursor/, .windsurf/, .claude/, and other tooling/config folders unless explicitly requested).

Workflow

Follow the detailed workflow in references/workflow.md. Use these guardrails when adapting it to a standalone repo: