What problem does it solve? Code reviews often conflate two separate questions — whether the code follows project conventions and whether it actually implements what was asked — letting one axis mask failures in the other. This Skill separates them into independent parallel reviews so neither can hide the other's findings. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (repo conventions plus a fixed Fowler code-smell baseline) and a Spec review (fidelity to the originating issue or spec) as parallel sub-agents, then aggregates both reports side by side. - Fixed-point diffing: Reviews changes since any commit, branch, tag, or merge-base using a 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, a user-supplied path, or files under docs/, specs/, or .scratch/. - Use Case: Before opening a pull request, ask for a review of your feature branch against main and receive separate Standards and Spec verdicts, each with its own findings and worst issue. ## Quick Start Ask the agent to review the changes on my current branch since main against our coding standards and the linked issue spec.
