# Code Review Severity Levels

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

**Field:** Artificial Intelligence  
**Category:** Claude Code  
**Also known as:** Important, Nit, Pre-existing

## Think of it like

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

## 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.

## 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.

## Common mistake

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

## Three principles

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

## Related terms

- [Claude Code Review](https://learn.benibix.com/term/ai/claude-code-review)
- [REVIEW.md](https://learn.benibix.com/term/ai/review-md)

![Three marks, from most to least urgent: Important for a bug to fix before merging, Nit for a small issue, Pre-existing for a bug that was already there.](https://learn.benibix.com/diagrams/ci-review-severity.svg)

---

Source: https://learn.benibix.com/term/ai/code-review-severity
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
