What problem does it solve? Reviewing a branch or PR requires checking two separate questions at once: does the code follow the repo's standards, and does it actually implement what the issue asked for. Mixing both in one review lets one axis mask the other, and doing it manually against a large diff is slow and inconsistent. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (repo-documented rules plus a fixed Fowler code-smell baseline) and a Spec review (requirements coverage, scope creep, wrong implementations) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Reviews the changes since any commit, branch, tag, or merge-base using git diff <fixed-point>...HEAD, with early validation that the ref resolves and the diff is non-empty. - Spec source discovery: Locates the originating spec from issue references in commit messages, a user-supplied path, or spec files under docs/, specs/, or .scratch/. - 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, plus a per-axis summary. ## Quick Start Ask the agent to review this branch since main using the code-review skill and report standards and spec findings separately.
