What problem does it solve? Reviewing a branch or PR requires checking two separate things — whether the code follows the project's standards and whether it actually implements what was asked — and doing both in one pass often means one concern pollutes the other or gets skipped entirely. ## Core Features & Use Cases - Two-axis review: Runs a Standards axis (repo-documented standards plus a fixed Fowler code-smell baseline) and a Spec axis (does the diff match the originating issue or PRD) as parallel sub-agents, then reports them side by side without merging or reranking. - 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: Automatically locates the originating spec from issue references in commit messages (via gh), user-provided paths, or spec files under spec/, docs/, or specs/. - Use Case: Before merging a feature branch, ask for a review since main and receive separate Standards and Spec reports, each citing the violated rule or spec line, with hard violations distinguished from judgement calls. ## Quick Start Ask the assistant to review the changes since main using the code-review skill and point it to the relevant issue or spec file.
