PR review rubric
What a staff-plus engineer looks at when reviewing.
1. Understand before commenting
- Read the PR description. If there isn't one, that's the first problem.
- Skim commits. A clean story of atomic commits tells you what the author was thinking.
- Read the tests first — they describe the contract.
- Now read the code.
If you can't state what this PR does in one sentence in your own words, you can't review it yet.
2. Correctness
- Does the happy path do what the desc
[Description truncada. Veja o README completo no GitHub.]