I used to leave 15 comments on every pull request. Half were about semicolons. My team started dreading my reviews.

Problem

Reviewers spend their limited attention flagging formatting and style nitpicks. That slows down review cycles, creates friction with the author, and crowds out the logic and architecture issues that actually matter.

Why it happens

• Style issues are easy to spot and feel productive to comment on
• Real correctness and design issues take more mental effort to find, so reviewers unconsciously default to the easy wins
• A long comment thread of nitpicks reads as “thorough” even when it caught nothing that would’ve broken production

Better approach

• Automate style and formatting completely with a linter and formatter running in CI or on save, so it’s never a human decision
• Treat any manual style comment as a bug in the linter config, not a review finding
• Reserve human review exclusively for logic, edge cases, architecture, and intent: the things a machine can’t judge

Example

After adding a formatter and linter to pre-commit hooks, one team’s average PR comment count dropped from 15 to 4. All 4 remaining comments were about actual bugs, not spacing or variable naming.