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. Doing both in one pass lets one concern mask the other, and findings get lost or reranked arbitrarily. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo conventions 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: Pins any commit, branch, tag, or merge-base the user supplies and validates the ref and non-empty 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 smells, and a Spec report quoting unmet requirements, side by side. ## Quick Start Ask the assistant to review the changes since main using the code-review skill and point it to the issue or spec file for the feature.
