Try for free

Guides

Code review comment examples: real comments, useful and noisy

A useful code review comment names the line, the input that breaks it, what happens, and the fix. The comments below are real: IonWarp's Code Review agent, on DeepSeek V4.1 Flash, posted them on open-source pull requests in our benchmark.

On 50 pull requests it found 77 of the 158 known issues, and 78 of its comments matched none.[1] A comment that matches no known issue is not proof it is wrong, but it is the kind a reader learns to skip.

Updated

Three real comments: two that found a bug, one that matched nothing

  • “Unhealthy flusher process is never killed for spawn-context processes”

    Sentry #93824, flusher.py line 254. Matched a known issue. It names the process type that makes the new isinstance check always false, what follows (a hung process keeps running beside its replacement), and the fix. Qodo, Greptile, Bugbot and CodeRabbit did not post it.[2]

  • “Non-atomic retry counter increment loses updates across overlapping runs”

    Cal.com #14943, scheduleSMSReminders.ts line 184. Matched a known issue. It says when it breaks (two cron runs overlap), what happens (an increment is lost and the same SMS is scheduled twice) and the fix: increment in the database. Bugbot, Greptile and Qodo did not post it.[3]

  • “Hard-backpressure check issues one cluster INFO query per flusher process”

    Sentry #93824. Matched no known issue. It applies only when two settings are changed from their defaults, as the comment itself notes, and it changes no decision, only the number of queries.[2]

What the useful comments have in common

  1. The line and the trigger

    The file, the line, and the input or event that breaks it: two cron runs that overlap, a process started with the spawn context.

  2. What happens

    What a user or an operator sees: a lost count, a duplicate SMS, a hung process that is never killed.

  3. The fix

    One change the author can make: increment the counter in the database, check the process's real base type. Reviewers' shorthand is decoded in PTAL, nit and LGTM.

FAQ

Quick answers

What makes a good code review comment?

It names the line, the input that breaks it, what happens, and a concrete fix. A reviewer can check it in a minute, and the author can act on it without asking a question.

What is a noisy code review comment?

One the author has to read in full to learn that nothing breaks, such as a cost that only appears with non-default settings.

How do I mark a comment that does not block the merge?

Start it with "Nit:", and submit the review as Comment rather than Request changes. IonWarp labels each finding P0, P1 or P2; a P2 is real but can wait, and the review comment lists it as a nitpick.

Did a person write these comments?

No. DeepSeek V4.1 Flash posted each one on a benchmark pull request, and Claude Opus 4.5 graded it against that pull request's known issues.

A first reviewer on every pull request.

Try for free

See pricing