Doing Code Review

Review is evidence-based risk reduction.

The goal is not perfection. Approve a change when it definitely improves overall code health, even if it is not exactly how you would have written it.

doing-code-review  (you are here)
  -> understand contract and verification story
  -> inspect diff, tests, and applicable risk axes
  -> findings?
       ├── yes -> receiving-code-review -> focused fixes -> focused verification
       └── no  -> verification-before-completion / approve with residual risks

Core Rules