Skip to content

Review code before you merge

Find the defects in a change you didn't write, with no nitpicks about style.

People usually start with: A pull request or diff

Ready now · a step-by-step playbook for thisUnderstand and review a codebaseA map of an unfamiliar repository, then a review that finds real bugs in a change — not style nits.3 steps · About 30 minutes · For developers

The Launch7 helper (coming)

Step by step: Ship a code change safely

Tests that catch real bugs, then a review that finds what's left. Fits inside your normal pull request.

  1. Plan before you build (optional) — Plan Before You Build, coming soon
  2. Write tests that catch bugs — Tests That Catch Bugs, coming soon
  3. Review the change — Code Review That Finds Real Bugs, coming soon
  4. Find the root cause if it breaks (optional) — Root-Cause Debugger, coming soon
See the guide (some steps coming)

Not quite your task? See everything in Build software or describe it in your own words.