What problem does it solve? Code review often conflates two separate questions — whether code follows project conventions and whether it implements what was actually requested — letting one axis mask failures in the other. This Skill separates those concerns into two independent reviews of the same diff. ## 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 spec file) as parallel sub-agents that don't pollute each other's context. - Fixed-point diffing: Reviews changes since any commit, branch, tag, or merge-base using three-dot git diff, with upfront validation that the ref resolves and the diff is non-empty. - Spec discovery: Locates the originating spec from issue references in commit messages, user-provided paths, or spec 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, reported side by side. ## Quick Start Ask the agent to review the changes since main on the current branch against the repo's coding standards and the originating issue.