PR Size

In one sentence

PR size is the amount of change in a pull request—usually measured in files, lines, or cognitive scope—and larger PRs are harder to review thoroughly.

Why it matters

Oversized PRs hide risk. Reviewers skim, miss high-risk hunks, and rubber-stamp agent-generated bulk edits that look tidy in the summary.

How it works

• Measure size with more than one signal: changed files, net lines, and whether the change spans multiple concerns.
• Prefer single-purpose PRs: one behavior change, one migration, or one dependency bump—not all three.
• Split generated noise and mechanical renames from intentional logic when possible.
• If a large PR is unavoidable, require a review map: risk areas first, then tests, then the rest.

Example

A 40-file PR that “cleans up types,” upgrades a library, and changes auth middleware is three reviews bundled as one. Ask for a split—or review auth and dependency changes before cosmetic edits.