Reducing False Positives
Temporarily disable high-noise categories.
The False-Positive Problem
You wired Claude Code into your CI pipeline to review every pull request. It works — but developers start ignoring it. Why? Too much noise. The review keeps flagging things that are not real problems: style nitpicks, harmless TODO comments, defensive null checks.
This is the false-positive problem. A reviewer that cries wolf gets muted. In Scenario 5 (Claude Code for CI/CD), one of the core architect skills is minimizing false positives so the signal that remains is trustworthy.
In this lesson you'll learn a fast, surgical tactic: temporarily disable high-noise categories so the review stays useful while you tune the real rules.
Why Noise Kills Trust
A CI reviewer has exactly one job: surface issues a human should act on. The moment it produces more false alarms than real findings, two things happen:
- Developers stop reading the comments.
- Real bugs hide inside the noise (lost-in-the-middle: attention drops on the long middle of a list).
Aggregate "we found 40 issues" sounds productive, but if 35 are noise the review has negative value — it costs attention and returns little. Reducing false positives is not cosmetic; it protects the credibility of the whole pipeline.
All lessons in this course
- Explicit Criteria over Vague Instructions
- Categorical Examples
- Severity Criteria with Examples
- Reducing False Positives