What problem does it solve? Reviewing a branch or PR requires checking two separate things at once: whether the code follows the repo's documented standards and whether it actually implements what the issue or spec asked for. Doing both in one pass lets one concern mask the other, so findings get lost or misranked. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo conventions 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 without merging or reranking. - Fixed-point diffing: Compares HEAD against any user-supplied commit, branch, tag, or merge-base using a three-dot git diff, validating the ref and non-empty diff before spawning reviewers. - Spec discovery: Locates the originating spec from issue references in commit messages, a user-provided 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, with a one-line summary per axis. ## Quick Start Ask the assistant to review the changes since main on the current branch using the code-review skill.
