What problem does it solve? Reviewing a branch or PR requires checking two separate things—whether the code follows the repo's documented standards and whether it actually implements what the issue or spec asked for—and doing both in one pass lets one concern mask the other. ## Core Features & Use Cases - Two-axis review: Evaluates the diff since a fixed point (commit, branch, tag, or merge-base) separately for Standards conformance and Spec fidelity, reporting them side by side without merging or reranking findings. - Isolated parallel reviewers: Delegates each axis to a separate Pi subagent with a fresh context and read-only tools, writing results to dedicated artifact files under .scratch/pi-agents/. - Fowler smell baseline: Applies a fixed set of code smells from Refactoring (Duplicated Code, Feature Envy, Shotgun Surgery, and more) even when the repo documents no standards, with repo rules always taking precedence. - Use Case: Before merging a feature branch, ask for a review since main and receive a Standards report and a Spec report, each with its own findings and worst issue, so a spec-compliant but sloppy change (or vice versa) is never hidden. ## Quick Start Ask the agent to review the changes since main on the current branch using the code-review skill.
