What problem does it solve? Reviewing a branch or PR requires checking two independent things at once: whether the code follows the repo's documented standards and whether it actually implements what the originating issue or spec asked for. Doing both in one pass lets one concern mask the other, and findings get lost. ## 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, incorrect implementations) as parallel sub-agents, then reports them side by side without merging or reranking. - Fixed-point diffing: Pins any commit, branch, tag, or merge-base the user supplies and reviews git diff <fixed-point>...HEAD, validating the ref and diff before spawning reviewers. - Automatic spec discovery: Locates the originating spec from issue references in commit messages, a user-provided path, or spec files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main and receive a ## Standards report citing violated conventions and code smells, plus a ## Spec report quoting unmet or over-delivered requirements. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
