Skip to content
BENIBIX Learn

Code Review Severity Levels

AI⌨️ Claude CodeIntegrations

Also known as Important, Nit, Pre-existing

The three marks a Code Review gives each thing it finds.

Think of it like

It is like traffic lights for problems. Red means stop. Yellow means take care.

Example

Jack's review shows one red finding and three yellow ones. He fixes the red one before merging and leaves the nits for later.

Why it matters

The marks tell you what must be fixed now and what can wait.

Definition

Code Review marks each finding with one of three levels. Important, in red, is a bug that should be fixed before merging. Nit, in yellow, is a small issue worth fixing but not blocking. Pre-existing, in purple, is a bug that was already in the code before this pull request. You can change how your repository ranks them in a REVIEW.md file.
Red, yellow and purple marks on a review's findings.

Common mistake

Treating a Pre-existing finding as something your change broke. It was there before, so it can be a separate fix.

Key takeaways

  1. 1
    Important. Fix before merging.
  2. 2
    Nit. Small, not blocking.
  3. 3
    Pre-existing. Was already there.