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

# Third-party tools overview

> Integrate 50+ third-party tools like ESLint, Ruff, and Betterleaks into CodeRabbit reviews for enhanced code quality.

All Platforms (This feature is available on all supported platforms: GitHub, GitLab, Azure DevOps, and Bitbucket.) | Essentials Plan (This feature is available on Essentials (formerly Pro), Team (formerly Pro+), Advanced, and Enterprise. Please refer to our pricing page for more information about our plans and features.)

CodeRabbit integrates with [50+](https://docs.coderabbit.ai/tools/list.md) third-party linters and security analysis tools to enhance your code reviews. These tools run automatically in secure sandboxed environments, and CodeRabbit uses their findings to inform its review comments.

## Default behavior

Almost all tools are enabled by default. CodeRabbit automatically determines which tools are relevant for each project, for example, PHP linters won't run on a Java project, and Rust linters won't run on a Python codebase. Tools are only invoked when the repository contains files they understand.

This means most projects require no tool configuration at all. The defaults work well out of the box. Configuration is typically only needed when you want to:

* **Disable a specific tool** that is not relevant or causes too much noise for your project.
* **Point to a non-default config file location**, for example if your ESLint config is in a custom path rather than the project root.

For details on how a specific tool behaves, what file types it targets, and what configuration options it supports, see that tool's individual page in the [tool catalog](https://docs.coderabbit.ai/tools/list.md).

## Configuration methods

### Individual tool settings

> [tab] YAML configuration
>
> Add tools to your repository's `.coderabbit.yaml` file:
>
> ```yaml .coderabbit.yaml lines wrap icon="code" theme={null}
> reviews:
>   tools:
>     eslint:
>       enabled: true
>     ruff:
>       enabled: true
>       config_file: "pyproject.toml"
> ```
>
> Use `reviews.tools.<tool>.enabled` to enable or disable individual tools. The optional `config_file` field points to your existing tool-specific configuration file (for example `.eslintrc.js` or `pyproject.toml`), letting you control which rules are active and their severity. See [specific tool guides](https://docs.coderabbit.ai/tools/list.md) for more detailed instructions.

> [tab] Settings page
>
> Configure tools through CodeRabbit's web interface:
>
> 1. Open your [organization defaults](https://docs.coderabbit.ai/configuration/web-app.md#edit-organization-defaults) or a [repository's settings](https://docs.coderabbit.ai/configuration/web-app.md), and go to **Reviews → Tools**. A repository's settings are read-only while [**Use organization settings**](https://docs.coderabbit.ai/configuration/web-app.md#choose-which-web-settings-a-repository-uses) is on; turn it off on the repository's **General** page to edit them
> 2. Toggle individual tools on/off
> 3. Apply your changes. For a repository, check your edits in [**Review changes**](https://docs.coderabbit.ai/configuration/web-app.md#save-and-review-changes) before you click **Submit changes**, especially after turning off **Use organization settings**, which activates the repository's saved settings without copying your organization defaults. To see which settings win when a repository also has a configuration file or global overrides, see [How CodeRabbit resolves configuration](https://docs.coderabbit.ai/configuration/resolution.md)

### Configuration files

When a tool-specific configuration file is present in your repository (such as `.eslintrc.js` or `pyproject.toml`), CodeRabbit uses it as-is. When no configuration file is found, most tools fall back to a profile-based default configuration so reviews still run without any setup required.

### Profiles

CodeRabbit offers two review profiles that control tool strictness:

* `Chill`: Focuses on critical issues and reduces noise from minor style violations
* `Assertive`: Provides comprehensive feedback including style and best practice suggestions

  ```yaml .coderabbit.yaml lines wrap icon="code" theme={null}
  reviews:
    profile: assertive
  ```

## Tool findings in reviews

CodeRabbit doesn't post each tool finding as its own comment. It passes the findings to the review model as hints, and the model checks each one against the code in context. The model decides which findings lead to review comments and leaves out false positives.

When an inline review comment covers lines that have tool findings, CodeRabbit adds a collapsed **🧰 Tools** section to the end of that comment. The section groups the findings by tool and shows each finding's severity, line range, message, and rule ID:

```text wrap icon="code" theme={null}
🧰 Tools
  🪛 ESLint
    [error] 12-12: 'React' must be in scope when using JSX

    (react/react-in-jsx-scope)
```

The **🧰 Tools** section lists only the findings on the lines that the comment covers. Comments that CodeRabbit collects in the review body, such as nitpicks, don't include it. A finding that no inline comment covers doesn't appear in any review comment. To see those findings too, set [`reviews.review_details`](https://docs.coderabbit.ai/reference/configuration#param-reviews-review-details) to `true`. The Walkthrough (A structured comment posted by CodeRabbit at the top of every pull request, summarizing changes, sequence diagrams, review effort, and more.) comment then lists tool findings in the changed code under [**Review details**](https://docs.coderabbit.ai/pr-reviews/walkthroughs.md#review-details) > **Additional context used**, grouped by tool and file.

> [!NOTE]
>
> On Bitbucket Cloud and Bitbucket Data Center, review comments don't include the **🧰 Tools** section.

## What's next

> [card] [Tool catalog](https://docs.coderabbit.ai/tools/list.md)
>
> Browse all linters, security analyzers, and CI/CD integrations by category and technology.

> [card] [Tool configuration reference](https://docs.coderabbit.ai/tools/reference.md)
>
> See every YAML configuration option for each supported tool.

> [card] [YAML configuration](https://docs.coderabbit.ai/reference/configuration.md)
>
> Full reference for all `.coderabbit.yaml` configuration options.


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