Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Skip to main content
🐰 New: Triage — a self-updating cross-repository queue that prioritizes pull requests by value and risk, so you always know what to review next. Now in beta! Explore Triage →
Third-party tools overview
Integrate 50+ third-party tools like ESLint, Ruff, and Betterleaks into CodeRabbit reviews for enhanced code quality and 1-click fixes.
|
CodeRabbit integrates with 50+ third-party linters and security analysis tools to enhance your code reviews. These tools run automatically in secure sandboxed environments, providing detailed feedback and 1-click fixes for common issues.
Many tools provide 1-click fixes that CodeRabbit can apply directly to your pull request, streamlining the review process.
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.
Configuration methods
Individual tool settings
- YAML configuration
- Settings page
Add tools to your repository’s Use
.coderabbit.yaml file:.coderabbit.yaml
reviews:
tools:
eslint:
enabled: true
ruff:
enabled: true
config_file: "pyproject.toml"
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 for more detailed instructions.Configure tools through CodeRabbit’s web interface:
- Navigate to Reviews → Tools in your settings (use All Settings mode)
- Toggle individual tools on/off
- Save changes to apply across all repositories
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.coderabbit.yamlreviews: profile: assertive
Tool output and fixes
When tools detect issues, CodeRabbit attaches structured output under the “Review details” comment in your pull or merge request. Each entry shows the file path, line number, and the issue detected:ESLint
src/components/Button.tsx
12-12: 'React' must be in scope when using JSX
Add React import statement
(react/react-in-jsx-scope)
What’s next
Tool catalog
Browse all linters, security analyzers, and CI/CD integrations by category and technology.
Tool configuration reference
See every YAML configuration option for each supported tool.
YAML configuration
Full reference for all
.coderabbit.yaml configuration options.Was this page helpful?