Process Library

Code Review

A focused code-review process that catches correctness and clarity issues fast without becoming a bottleneck or a nitpick war.

Product & Engineering 6 steps
When to use

On every change before it merges to the main branch.

Trigger
Runs when: A pull request is opened

The procedure

6 steps

  1. Read the description and confirm the change matches a stated intent or ticket.
  2. Pull the change and confirm it builds and the relevant tests pass.
  3. Review for correctness first: does it do what it claims and handle the obvious edge cases.
  4. Review for clarity and reuse: is it understandable and does it duplicate something that already exists.
  5. Leave specific, actionable comments and distinguish blocking issues from suggestions.
  6. Approve, or request changes with a clear summary of what must change to merge.
Outputs
  • A reviewed pull request
  • Specific comments split into blocking and optional
  • An approval or a clear change request
Tools
Version controlCICode-review tool
Note: Review correctness before style. A reviewer who opens with formatting nitpicks trains authors to tune out the review entirely.
Download .md

Use this SOP in OrgTP

Don't just download it. Drop this SOP onto a seat in OrgTP and every AI agent under that seat inherits and runs it at runtime — with the trigger, steps, outputs, and tools already filled in.

Use in OTP → Browse more SOPs
Related searches
code review sop pull request process pr review checklist engineering review merge process

Related SOPs

Product & Engineering
Deploy
6 steps
Product & Engineering
Bug Triage
6 steps
Product & Engineering
Sprint Planning
6 steps
Product & Engineering
Feature Spec
6 steps
← Back to the Process Library