Slop Detection

Detect low-quality, AI-generated pull requests, with platform-specific author, plan, and labeling restrictions.

|

CodeRabbit analyzes pull requests and GitLab merge requests for signals of low-quality, AI-generated content. If the request is classified as slop, CodeRabbit adds a warning to the PR Walkthrough comment. On platforms that support labeling, you can also configure a label for flagged requests.

Slop Detection is enabled by default. Analysis runs on the first full review when the repository and author meet the requirements below. On GitHub, GitLab, and Azure DevOps, requests that still carry your configured slop label are checked again on subsequent reviews. Bitbucket does not support these label-based rechecks. Slop Detection does not run in IDE or CLI reviews.

Platform availability and restrictions

Private repositories require the Essentials plan or higher. Public GitHub, GitLab, and Bitbucket repositories are eligible on all plans. Azure DevOps requires the Essentials plan or higher even for public projects.

The following restrictions apply to eligible repositories. Setting include_all_authors: true includes authors who would otherwise be exempt because of their repository relationship.

Platform	Author exemptions by default	Labels and subsequent reviews
GitHub and GitHub Enterprise	Collaborators, contributors, organization members, and repository owners are exempt.	Applies the configured label and rechecks labeled PRs. Removes the label after a completed analysis finds neither spam nor slop.
GitLab and GitLab Self-Managed	Authors identified as project Developers, Maintainers, or Owners are exempt.	Applies the configured label and rechecks labeled merge requests. Remove the label manually after resolving the findings.
Azure DevOps Services	PRs from branches in the same repository require include_all_authors: true; their authors are treated as collaborators.	Applies the configured label and rechecks labeled PRs. Remove the label manually after resolving the findings.
Azure DevOps Server	Requires the Server integration to be enabled for your deployment; confirm availability with CodeRabbit support. The same author and plan restrictions as Azure DevOps Services apply when enabled.	The same labeling and recheck behavior as Azure DevOps Services applies when enabled.
Bitbucket Cloud	PRs from branches in the same repository require include_all_authors: true.	Use the PR Walkthrough warning. Do not rely on automatic labeling or label-based rechecks.
Bitbucket Data Center	PRs from branches in the same repository require include_all_authors: true.	Use the PR Walkthrough warning. PR labels and label-based rechecks are unavailable.

On Azure DevOps and Bitbucket, fork PRs are not excluded by the same-repository author rule. They still need to meet the plan and review requirements.

Configuration

Configuration file

Configure the slop_detection section in your .coderabbit.yaml file:

.coderabbit.yaml

reviews:
  slop_detection:
    enabled: true   # Runs automatically on eligible repos unless disabled
    include_all_authors: false
    label: "slop"   # Add a label to apply when slop is detected (no label applied by default)

Web UI

1. Go to CodeRabbit settings for your repository or organization.
2. Switch the mode (bottom-left) to All Settings.
3. Navigate to Reviews → General.
4. Scroll down to the Anti-Slop section to toggle Enabled or Include All Authors on or off, and optionally set a custom Label.

Disabling Slop Detection

To disable Slop Detection on a repository, set enabled to false or disable it in the web UI:

.coderabbit.yaml

reviews:
  slop_detection:
    enabled: false

Include all pull request authors

Author exemptions depend on the platform, as shown in the availability table. To analyze requests from otherwise exempt authors, including same-repository PRs on Azure DevOps and Bitbucket, set include_all_authors to true:

.coderabbit.yaml

reviews:
  slop_detection:
    include_all_authors: true

Recognized automation accounts, such as Dependabot and Renovate, remain exempt when this option is enabled. This exemption uses known account names; it does not cover every service or automation account.

Label flagged PRs

By default, Slop Detection only adds a warning to the PR Walkthrough comment. On GitHub, GitLab, and Azure DevOps, set the label field to also label flagged requests:

.coderabbit.yaml

reviews:
  slop_detection:
    label: "slop"   # Or any label name you prefer, e.g. "ai-spam"

The configured label also makes the request eligible for another analysis on subsequent reviews, subject to the same plan and author requirements. On GitHub, CodeRabbit removes this label after a completed analysis finds neither spam nor slop. On GitLab and Azure DevOps, remove it manually after resolving the findings. Bitbucket does not support label-based rechecks.

Frequently asked questions

Can I customize the detection criteria or thresholds?

No. You can enable or disable Slop Detection, choose a label on supported platforms, and include otherwise exempt authors with include_all_authors. Custom detection criteria and thresholds are not configurable.

Does Slop Detection work on private repositories?

Yes. Private repositories require the Essentials plan or higher. Public GitHub, GitLab, and Bitbucket repositories are eligible on all plans. Azure DevOps requires the Essentials plan or higher even for public projects. See the platform restrictions for author and integration requirements.

Are any pull request authors exempt?

Yes. The platform table lists the default author exemptions. Set reviews.slop_detection.include_all_authors to true to include those authors. Recognized automation accounts remain exempt.

Will Slop Detection block a PR from being merged?

No. Slop Detection does not block merges. When a PR is classified as slop, a warning is added to the PR Walkthrough comment. On platforms that support labeling, a configured label is also applied so maintainers can filter and triage PRs at their discretion.

Can I automatically close slop PRs?

Not at the moment. CodeRabbit is currently gathering data and tuning the detection mechanism to ensure accuracy.

What’s next

Pre-Merge Checks

Enforce quality gates and custom requirements before pull requests are merged

Automatic review controls

Fine-tune which PRs CodeRabbit reviews automatically using labels, branches, and author filters

Configuration reference

See the full slop_detection schema with types, defaults, and constraints