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

# Reduce review noise

> Lower the number of review comments with a quieter profile, file filters, targeted instructions, fewer incremental reviews and slimmer output.

If reviews feel noisy, change the settings that control volume first, then add instructions. This guide lists the levers from the biggest effect to the smallest. Apply them one at a time, so you can see which one helped.

## Before you start

* Check which profile is in effect. Post `@coderabbitai configuration` on a pull request and read `reviews.profile` and its `# Source:` comment. See [Check which configuration a review used](https://docs.coderabbit.ai/configuration/guides/check-effective-configuration.md).
* Decide where you change settings. For one repository, use the [configuration file](https://docs.coderabbit.ai/configuration/file.md) or [Repository settings](https://docs.coderabbit.ai/configuration/web-app.md). For every repository, see [Apply settings to every repository](https://docs.coderabbit.ai/configuration/guides/all-repositories.md).

## Lower the review profile

`reviews.profile` is the main volume control. It has three values.

| Profile | What CodeRabbit posts inline |
| - | - |
| `quiet` | Only critical and major comments with a high effort-to-reward ratio. The rest go into collapsed sections of the review summary. |
| `chill` (default) | Critical, major and minor comments, up to 20, then it collapses minor comments and then major ones. |
| `assertive` | Every severity, including trivial and informational comments. |

> [tab] In the app
>
> Open **Review > Review settings**, choose **Organization defaults** or a repository, open **Reviews > General**, and set the profile.

> [tab] YAML V2
>
> ```yaml theme={null}
> reviews:
>   profile: quiet
> ```

> [tab] YAML V3
>
> Early Access (This feature is in early access. Enable it by setting `early_access: true` in your `.coderabbit.yaml`, or by toggling Early Access on the web interface.)
>
> V3 is a limited preview. Adding `version: 3` doesn't give your organization access.
>
> ```yaml theme={null}
> version: 3
> reviews:
>   behavior:
>     profile: quiet
> ```

The profile also affects tools: only `assertive` switches CodeRabbit's generated fallback tool configurations to stricter rule sets.

## Exclude files that don't need review

Path filters remove files before CodeRabbit reviews them. Use exclusions only, so every other file stays in scope. An exclusion always wins. A single include pattern turns the list into an allowlist. The one exception restores a [default exclusion](https://docs.coderabbit.ai/pr-reviews/which-files.md#files-skipped-by-default): copy its exact pattern without the leading `!`. That turns off only that default. A broader pattern doesn't restore default-excluded files and creates an allowlist.

> [tab] YAML V2
>
> ```yaml theme={null}
> reviews:
>   path_filters:
>     - "!**/vendor/**"
>     - "!**/*.lock"
>     - "!**/dist/**"
> ```

> [tab] YAML V3
>
> Early Access (This feature is in early access. Enable it by setting `early_access: true` in your `.coderabbit.yaml`, or by toggling Early Access on the web interface.)
>
> V3 is a limited preview. Adding `version: 3` doesn't give your organization access.
>
> ```yaml theme={null}
> version: 3
> reviews:
>   behavior:
>     path_filters:
>       - "!**/vendor/**"
>       - "!**/*.lock"
>       - "!**/dist/**"
> ```

Default exclusions already cover common generated code. See [Choose which files are reviewed](https://docs.coderabbit.ai/pr-reviews/which-files.md).

## Tell CodeRabbit to skip style nits

Linters and formatting tools should own style. Add one path instruction that applies to every file and limits CodeRabbit to issues that matter.

```yaml theme={null}
reviews:
  path_instructions:
    - path: "**/*"
      instructions: |
        - Comment only on issues that block merging: bugs, security, data loss.
        - Ignore style and formatting. Linters cover them.
        - Mention a repeated pattern once, at summary level.
```

The pattern `**/*` matches every file, hidden files (names starting with a dot) included. An instruction only guides the model. The profile is the structural volume control, so use both. In V3, put the same text in a document in `.coderabbit/instructions/`. See [Instruction and check documents](https://docs.coderabbit.ai/configuration/documents.md).

## Leave style to your own linters

Turn off a tool that duplicates a linter you already run, or point it at your own configuration file. Use the tool's own config file for per-rule control. A profile change affects every tool. See [Tools](https://docs.coderabbit.ai/tools/index.md).

## Review fewer pushes

By default, CodeRabbit reviews every push as an incremental review and pauses after five reviewed commits. For active pull requests, lower the limit, as in this example:

> [tab] YAML V2
>
> ```yaml theme={null}
> reviews:
>   auto_review:
>     auto_pause_after_reviewed_commits: 2
> ```

> [tab] YAML V3
>
> Early Access (This feature is in early access. Enable it by setting `early_access: true` in your `.coderabbit.yaml`, or by toggling Early Access on the web interface.)
>
> V3 is a limited preview. Adding `version: 3` doesn't give your organization access.
>
> ```yaml theme={null}
> version: 3
> reviews:
>   auto_review:
>     pause_after_reviewed_commits: 2
> ```

`0` turns pausing off. The counter resets when a review resumes.

To stop automatic reviews of new pushes altogether, turn incremental review off instead: set `reviews.auto_review.auto_incremental_review` to `false` in V2, or `reviews.auto_review.incremental_review` to `false` in V3. To pause or resume a single pull request, comment `@coderabbitai pause` or `@coderabbitai resume`.

## Trim the output

Each of these V2 keys removes a section of the walkthrough or summary:

| V2 key | Default | V3 key |
| - | - | - |
| `reviews.high_level_summary` | `true` | `reviews.output.summary.placement` |
| `reviews.changed_files_summary` | `true` | `reviews.output.walkthrough.changed_files_summary` |
| `reviews.related_issues` | `true` | `reviews.output.walkthrough.related_issues` |
| `reviews.sequence_diagrams` | `true` | No V3 key: fixed at `false` |
| `reviews.poem` | `false` | No V3 key: fixed at `false` |

Keep `reviews.collapse_walkthrough` (V3 `reviews.output.walkthrough.collapse`) at `true` so the walkthrough stays collapsed. It hides the walkthrough but doesn't remove it.

`tone_instructions` (V2) or `fun.tone_instructions` (V3) changes how comments read, up to 250 characters. It isn't a volume control.

## Check the result

Compare the next few pull requests against recent ones. Look at the number of inline comments, the collapsed sections in the summary, and whether the comments you still get are the ones you want. If a useful comment disappeared, raise the profile one step or narrow the instruction.

## What's next

> [card] [Write review instructions that work](https://docs.coderabbit.ai/configuration/guides/write-instructions.md)
>
> Make the instructions you add specific, scoped and checkable.

> [card] [Set review strictness, tone and language](https://docs.coderabbit.ai/pr-reviews/review-style.md)
>
> Learn what the profile, tone and language settings change.

> [card] [Teach CodeRabbit your review rules](https://docs.coderabbit.ai/pr-reviews/review-instructions.md)
>
> Choose between path instructions, code guidelines and custom checks.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.