Hi! 👋 We are doing a big documentation refresh. Help us improve - what's missing or could be better? Let us know! Join the Discord channel or simply send an email!
Complete reference for CodeRabbit configuration options with detailed explanations, types, and examples.
This reference is automatically generated from the CodeRabbit configuration
schema. Last updated: 2026-01-30
CodeRabbit’s behavior can be customized using a .coderabbit.yaml file in your repository root. This reference covers all available configuration options with clear property names and examples.
Set the review profile: chill for lighter feedback, assertive for more feedback (which may feel nitpicky).One of the following: chill, assertiveDefaults to "chill".
Automatically approve once CodeRabbit’s comments are resolved and no pre-merge checks are failing. Note: In GitLab, all discussions must be resolved.Defaults to false.
By default, CodeRabbit generates release notes in the description. Use this to customize the summary content and format. Example: ‘Create concise release notes as a bullet-point list, followed by a Markdown table showing lines added and removed by each contributing author.’ Note: Use high_level_summary_in_walkthrough to place the summary in the walkthrough instead of the description.Defaults to "".
Placeholder in the PR description that CodeRabbit replaces with the high-level summary. If high_level_summary is false, the summary is still generated when this placeholder is present.Defaults to "@coderabbitai summary".
Labeling Instructions | Define allowed labels and when to suggest them. When provided, CodeRabbit suggests only from this list (still informed by prior PRs); when empty, suggestions rely entirely on prior PRs.Defaults to [].
Prompt for AI Agents | Include the ’🤖 Prompt for AI Agents’ section in inline review comments to provide codegen instructions for AI agents.Defaults to true.
Specify file patterns to include or exclude in a review using glob patterns (e.g., !dist/**, src/**). These patterns also apply to ‘git sparse-checkout’, including specified patterns and ignoring excluded ones (starting with ’!’) when cloning the repository.Defaults to [].
Keyword in the PR description that triggers a review when automatic reviews are disabled. If enabled is false and this field is not empty, CodeRabbit reviews the PR only when this keyword is present in the description.Defaults to "".
Labels that control which PRs are reviewed. Labels starting with ’!’ are negative matches. Examples: [‘bug’, ‘feature’] reviews PRs with either label. [‘!wip’] reviews all PRs except those labeled ‘wip’. [‘bug’, ‘!wip’] reviews PRs labeled ‘bug’ but not ‘wip’. This setting also triggers a review when enabled is false.Defaults to [].
Docstrings | Enable the docstrings finishing touch (trigger via the 📝 Generate docstrings checkbox or @coderabbitai generate docstrings). CodeRabbit generates or improves docstrings for functions changed in the PR and opens a follow-up PR containing the docstring edits.Defaults to true.
Mode | Enforcement level: off disables the check, warning posts a warning, and error requires resolution before merging. If the request-changes workflow is enabled, error can block the PR until the check passes.One of the following: off, warning, errorDefaults to "warning".
Mode | Enforcement level: off disables the check, warning posts a warning, and error requires resolution before merging. If the request-changes workflow is enabled, error can block the PR until the check passes.One of the following: off, warning, errorDefaults to "warning".
Mode | Enforcement level: off disables the check, warning posts a warning, and error requires resolution before merging. If the request-changes workflow is enabled, error can block the PR until the check passes.One of the following: off, warning, errorDefaults to "warning".
Mode | Enforcement level: off disables the check, warning posts a warning, and error requires resolution before merging. If the request-changes workflow is enabled, error can block the PR until the check passes.One of the following: off, warning, errorDefaults to "warning".
Custom Pre-merge Checks | Define up to 5 custom checks that must pass before merging. Each check needs a unique name (≤50 chars) and deterministic instructions (≤10,000 chars).Defaults to [].
Mode | Enforcement level: off disables the check, warning posts a warning, and error requires resolution before merging. If the request-changes workflow is enabled, error can block the PR until the check passes.One of the following: off, warning, errorDefaults to "warning".
Enable ast-grep | ast-grep is a code analysis tool that helps you to find patterns in your codebase using abstract syntax trees patterns. | v0.40.5Defaults to {}.
Enable markdownlint | markdownlint-cli2 is a static analysis tool to enforce standards and consistency for Markdown files. | Enable markdownlint integration. | v0.20.0Defaults to true.
If set to ‘picky’, additional rules will be activated, i.e. rules that you might only find useful when checking formal text.One of the following: default, pickyDefaults to "default".
Optional path to the SwiftLint configuration file relative to the repository. This is useful when the configuration file is named differently than the default ‘.swiftlint.yml’ or ‘.swiftlint.yaml’.
Enable PHPStan | PHPStan requires config file in your repository root. Please ensure that this file contains the paths: parameter. | v2.1.37Defaults to true.
Level | Specify the rule level to run. This setting is ignored if your configuration file already has a level: parameter.One of the following: default, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, maxDefaults to "default".
Optional path to the golangci-lint configuration file relative to the repository. Useful when the configuration file is named differently than the default ‘.golangci.yml’, ‘.golangci.yaml’, ‘.golangci.toml’, ‘.golangci.json’.
Enable Semgrep | Semgrep is a static analysis tool designed to scan code for security vulnerabilities and code quality issues. | Enable Semgrep integration. | v1.149.0Defaults to true.
Enable Shopify Theme Check | A linter for Shopify themes that helps you follow Shopify theme & Liquid best practices | cli 3.89.0 | theme 3.58.2Defaults to true.
Blinter is a linter for Windows batch files that provides comprehensive static analysis to identify syntax errors, security vulnerabilities, performance issues, and style problems.Defaults to {}.
Enable Blinter | Blinter is a linter for Windows batch files that provides comprehensive static analysis to identify syntax errors, security vulnerabilities, performance issues, and style problems. | v1.0.102Defaults to true.
Jira | Allow creating Jira issues from chat. ‘auto’ disables the integration for public repositories.One of the following: auto, enabled, disabledDefaults to "auto".
Linear | Allow creating Linear issues from chat. ‘auto’ disables the integration for public repositories.One of the following: auto, enabled, disabledDefaults to "auto".
File Patterns | Patterns for your coding guideline documents. CodeRabbit scans these files to learn your standards and apply them during reviews. Multiple files supported; file names are case-sensitive. Defaults include: (**/.cursorrules, .github/copilot-instructions.md, .github/instructions/.instructions.md, **/CLAUDE.md, **/GEMINI.md, **/.cursor/rules/, **/.windsurfrules, **/.clinerules/, **/.rules/, **/AGENT.md, **/AGENTS.md).Defaults to [].
Learnings | Choose scope: ‘local’ (repo), ‘global’ (org), or ‘auto’ (local for public repos, global for private repos).One of the following: local, global, autoDefaults to "auto".
Issues | Choose scope for GitHub/GitLab issues: ‘local’ (repo), ‘global’ (org), or ‘auto’ (local for public repos, global for private repos).One of the following: local, global, autoDefaults to "auto".
Jira | Use Jira as a knowledge source. ‘auto’ disables the integration for public repositories.One of the following: auto, enabled, disabledDefaults to "auto".
Linear | Use Linear as a knowledge source. ‘auto’ disables the integration for public repositories.One of the following: auto, enabled, disabledDefaults to "auto".
PRs | Choose scope: ‘local’ (repo), ‘global’ (org), or ‘auto’ (local for public repos, global for private repos).One of the following: local, global, autoDefaults to "auto".
MCP | Use MCP servers as a knowledge source. ‘auto’ disables the integration for public repositories.One of the following: auto, enabled, disabledDefaults to "auto".
Disabled MCP Servers | Specify MCP server labels to disable (case-insensitive). These servers will be excluded from reviews and knowledge base queries.Defaults to [].
Labels that trigger automatic issue planning. Labels starting with ’!’ are negative matches. Examples: [‘feature’, ‘enhancement’] plans issues with either label. [‘!wip’] plans all issues except those labeled ‘wip’. [‘feature’, ‘!wip’] plans issues labeled ‘feature’ but not ‘wip’.Defaults to [].
Automatically apply suggested labels to the issue. When enabled without labeling instructions, labels are auto-suggested based on similar issues.Defaults to false.
