What problem does it solve? Reviewing a branch or PR requires checking two separate things — whether the code follows the repo's documented standards and whether it actually implements what the originating 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 Fowler code-smell baseline) and a Spec review (requirements coverage, scope creep, incorrect implementations) as parallel sub-agents, then reports them side by side without merging or reranking. - Fixed-point diffing: Reviews the changes between HEAD and any commit, branch, tag, or merge-base the user supplies, validating the ref and diff before spawning agents. - Spec discovery: Locates the originating spec from issue references in commit messages, a user-supplied path, or PRD files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main — you get a Standards report citing violated conventions and code smells, plus a Spec report quoting requirement lines that are missing, partial, or out of scope. ## Quick Start Ask the assistant to review the changes on this branch since main against the repo's coding standards and the originating issue.
