# Code Review

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

**Category:** Product & Engineering

**When to use:** On every change before it merges to the main branch.

**Trigger:** A pull request is opened

## 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 control
- CI
- Code-review tool

## Notes

Review correctness before style. A reviewer who opens with formatting nitpicks trains authors to tune out the review entirely.

---

Free SOP from the OrgTP Process Library — https://orgtp.com/process-templates/code-review
Run it live with your humans and AI agents at https://orgtp.com.