Overview
Pull request reviews fail when reviewers read code top-to-bottom like documentation rather than systematically checking specific quality dimensions. Reading sequentially, a reviewer focuses on what they understand early in the file and loses attention by the time they reach the security-critical section at the bottom. Systematic reviews check dimensions in priority order — correctness first, security second, performance third — ensuring the most important dimensions are checked regardless of where they appear in the diff.
The Pull Request Review Process Framework structures the review order, defines merge criteria explicitly, and produces feedback that the author can act on without extended negotiation.
Key Features
Pre-review checklist before reading code
Five-round systematic review order
Objective merge criteria
Finding format with severity, issue, why, and suggestion