> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kodus.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Review Filters

> Control how much feedback Kody posts in your PRs.

Review filters decide **which** of Kody's findings actually get posted. You'll find them under
**Settings → Code Review → the repository → Review filters**, and they can be set at the global,
repository, or directory level — see
[Config Inheritance & Overrides](/en/how_to_use/code_review/configs/inheritance_overrides).

## Minimum severity level

Kody assigns a severity to every suggestion and only posts the ones at or above the level you
pick. The default is **Medium**.

| Level                | What it covers                                                                                                                                  |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Low / All**        | Minor enhancements that would improve code quality — small optimizations, style improvements, subtle refinements.                               |
| **Medium** (default) | Moderate improvements that are recommended but not immediately critical: best practices, preventing future technical debt.                      |
| **High**             | Significant issues that should be addressed in the near term — important quality improvements, potential risks, substantial technical concerns. |
| **Critical**         | Issues that require immediate attention and could severely impact stability, security, or functionality.                                        |

<Tip>
  Too much noise on a big PR is usually a severity problem, not a volume problem. Move to
  **High** before reaching for anything else — you keep every real bug and drop the nitpicks.
  See [Reduce code review noise](/en/knowledge_base/how-to-reduce-code-review-noise).
</Tip>

## Apply filters to Kody Rules

A toggle, **off by default**.

* **Off** — [Kody Rules](/en/how_to_use/code_review/configs/kody_rules) findings **bypass** the
  severity filter. A rule your team wrote is always reported, whatever severity it lands on.
* **On** — Kody Rules go through the same severity filter as every other suggestion.

Leave it off unless your rules are producing more noise than signal. The whole point of a Kody
Rule is that your team already decided it matters.

<Note>
  In `kodus-config.yml` these two settings live under `suggestionControl`:

  ```yaml theme={null}
  suggestionControl:
      severityLevelFilter: 'medium' # low | medium | high | critical
      applyFiltersToKodyRules: false
  ```

  Remember that the file is only read once you enable
  `kodusConfigFileOverridesWebPreferences` — see
  [General](/en/how_to_use/code_review/configs/general).
</Note>

## Other ways to cut noise

Review filters are a blunt instrument. When you need something more targeted:

* **Ignore paths** — skip generated code, lockfiles, and vendored directories entirely.
  See [General](/en/how_to_use/code_review/configs/general).
* **Analysis types** — turn off a whole category (e.g. `performance`) for repositories where it
  isn't useful.
* **Directory-level config** — apply stricter or looser filters per folder in a monorepo.
  See [Directory Level Config](/en/how_to_use/code_review/configs/directory_level).
* **Kody Rules** — encode what your team actually cares about, so the signal comes from your
  standards instead of generic advice.