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 issue or PRD asked for — and mixing both concerns in one pass lets one axis mask failures in 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 from the originating issue or PRD) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Compares HEAD against any commit, branch, tag, or merge-base the user supplies, validating the ref and diff before spawning reviewers. - 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 listing missing requirements and scope creep, each under its own heading. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
