Review PR

Forensic, stage-aware pull request review. Reconstructs the commit narrative, tests the PR's architectural premises against project reality, and produces a review comment the user can post directly.

Three core insights:

1. Most bad reviews happen because the reviewer looks at the final diff in isolation and misses the why.
2. Most over-engineered PRs happen because the contributor builds for imagined future requirements instead of the current problem.
3. Most shallow reviews happen because the reviewer catalogs file-level findings without first understanding what the change means for the product. Think about the product impact before diving into the code.

Phase 1 — Orientation

Before reading any code, establish context.