What problem does it solve? Reviewing a branch or PR requires checking two separate concerns at once—whether the code follows the repo's documented standards and whether it faithfully implements the original spec—and mixing them in one pass lets one axis mask failures in the other. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo conventions plus a Fowler code-smell baseline) and a Spec review (requirements coverage, scope creep, incorrect implementations) as parallel sub-agents that don't pollute each other's context. - Fixed-point diffing: Pins any commit, branch, tag, or merge-base the user supplies and reviews the three-dot diff against HEAD, validating the ref and non-empty diff before spawning agents. - Spec source discovery: Locates the originating spec from issue references in commit messages, a user-provided path, or files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main; you receive separate Standards and Spec reports with per-file findings, quoted spec lines, and a one-line summary of the worst issue per axis. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
