What problem does it solve? Reviewing a branch or PR requires checking two independent things at once: whether the code follows the repo's documented standards, and whether it actually implements what the originating issue or spec asked for. Doing both in one pass lets one axis mask the other, so findings get lost or misranked. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (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: Pins any commit, branch, tag, or merge-base the user supplies and validates it before spawning reviewers, so bad refs fail fast. - Spec 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: After finishing a feature branch, ask to "review since main" and receive a Standards report citing violated conventions and smells, plus a Spec report quoting unmet or over-built requirements. ## Quick Start Ask the assistant to review the changes since main using the code-review skill, pointing it at the issue or spec the branch implements.
