Skip to main content
Basic Semi-formal IVT

code review

A systematic peer examination of source code changes before they are merged, aimed at identifying bugs, enforcing standards, and sharing knowledge.

Full Definition

A code review is a quality-assurance practice in which one or more developers examine a colleague's proposed code changes—typically submitted as a pull request or merge request—to identify defects, verify adherence to coding standards, and ensure architectural alignment. In documentation, 'code review' is two words, unhyphenated as a noun phrase; it becomes 'code-review' (hyphenated) when used as a compound modifier before a noun (e.g., 'the code-review process'). Editors should not conflate code review with automated testing, linting, or pair programming.

Usage

Usage note: Two words, no hyphen as a noun: 'code review'. Hyphenate as a modifier: 'code-review checklist'. Do not italicise or quote-mark in standard prose.

In Context

  • "No branch may be merged without at least two approvals from the code review process." — Engineering contribution guide
  • "The style guide required 'code-review guidelines' (hyphenated modifier) rather than 'code review guidelines'." — Style guide annotation

Also known as

peer review PR review code inspection

Don't confuse with

pair programming automated testing linting

Editors from these organisations have used our services since 1998

Reuters BBC Oxford University Press Penguin Random House Springer Microsoft Suncor Energy United Nations Fisher Investments IBM The Home Depot KODAK CHEVRON