What problem does it solve? Code reviews often conflate two different questions: does the code follow the project's conventions, and does it actually implement what was asked? This Skill separates those concerns into two independent review axes so a failure in one cannot be masked by a pass in the other, and so findings are grounded in cited standards and spec lines rather than vague opinion. ## Core Features & Use Cases - Two-axis review: Runs a Standards axis (documented repo conventions plus a fixed Fowler code-smell baseline) and a Spec axis (requirements coverage, scope creep, incorrect implementations) as parallel sub-agents or sequentially. - Flexible change-set selection: Reviews pull requests, committed ranges (three-dot merge-base or exact two-dot diffs), and WIP working-tree changes including staged, unstaged, and untracked files. - Automatic spec and standards discovery: Locates the originating issue, PRD, or spec file and the repo's coding standards documents, falling back to a general baseline when none exist. - Use Case: Before merging a feature branch, ask for a review against the original issue. You receive a ## Standards report citing violated conventions and smells, and a ## Spec report quoting unmet requirements, plus a one-line summary per axis. ## Quick Start Review this branch against the original issue and the repository standards, and report findings under separate Standards and Spec headings without editing any files.
