pr-review

# PR Review — Two-Axis, Stack-Agnostic Deep Code Review ## Philosophy The purpose of reviewing a change is to build **shared understanding** of what the change is trying to do, then systematically hunt for the bugs and edge cases that intent reveals. Every diff carries implicit assumptions, unstated invariants, and ambiguous decisions. The review walks through them one by one. When neither the codebase nor the user can resolve a question deterministically — when it's a real unknown about author intent or non-local context — that question itself becomes a review comment for the author to answer. The goal is **zero unexamined assumptions** before the review is finalized. ### The two review axes (Standards ⊥ Spec) The diff is checked along **two deliberately separate axes** by parallel, context-isolated sub-agents (Phase 3.5): - **Standards** — does the code conform to *this repo's* documented conventions (discovered in Phase 0)? - **Spec** — does the code faithfully implement the originating spec / issue / story / PRD? A change can pass one axis and fail the other: - Code that follows every standard but implements the wrong thing → **Standards pass, Spec fail.** - Code that does exactly what the issue asked but breaks the project's conventions → **Spec pass, Standards fail.** The two axes run as **separate sub-agents** so neither pollutes the other's context, and their findings are reported **side by side, never merged or reranked across axes** — separation stops one ax...