What problem does it solve? Code reviews often conflate two separate questions — whether code follows project conventions and whether it implements what was actually requested — causing one axis to mask failures in the other. This Skill separates those concerns into independent parallel reviews so neither axis hides the other's findings. ## 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 with isolated contexts. - Fixed-point diffing: Pins any commit, branch, tag, or merge-base as the comparison point and validates it before spawning reviewers. - Spec discovery: Automatically 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, each summarized separately. ## Quick Start Review the changes on my current branch since main against our coding standards and the linked issue spec.
