What problem does it solve? Reviewing a branch or PR requires checking two independent things — whether the code follows the repo's documented standards and whether it actually implements what the issue or PRD asked for — and doing both in one pass lets one concern mask the other. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo standards plus a fixed Fowler code-smell baseline) and a Spec review (requirements coverage, scope creep, incorrect implementations) as parallel sub-agents that don't pollute each other's context. - Fixed-point diffing: Reviews the changes since any commit, branch, tag, or merge-base the user supplies, validating the ref and diff before spawning reviewers. - Spec source discovery: Locates the originating spec from issue references in commit messages, a user-provided path, or PRD files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main and receive side-by-side Standards and Spec reports, each citing the violated rule or spec line. ## Quick Start Ask the agent to review the changes on this branch since main using the code-review skill.
