What problem does it solve? Reviewing a branch or PR requires checking two independent questions at once: does the code follow the repo's documented standards, and does it actually implement what the issue or spec asked for. Doing both in one pass lets one axis mask the other, so problems slip through. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo conventions plus a Fowler code-smell baseline) and a Spec review (requirements coverage, scope creep, wrong implementations) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Compares HEAD against any user-supplied commit, branch, tag, or merge-base using three-dot git diff, with upfront validation of the ref and diff. - Spec discovery: Locates the originating spec from issue references in commit messages, user-provided paths, or files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main and receive separate 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 against the repo's coding standards and the originating issue.