Skip to main content
| When a pull request is opened on a public GitHub repository, CodeRabbit analyzes the changes for signals of low-quality, AI-generated content. If the PR is classified as slop, CodeRabbit notes this in the PR Walkthrough comment. Additionally, you can configure a label in your settings to get the suspicious PRs labeled automatically. The detection runs as part of CodeRabbit’s standard review pipeline, no additional setup is required.

Configuration

Configure the slop_detection section in your .coderabbit.yaml file:
.coderabbit.yaml
reviews:
  slop_detection:
    enabled: true   # Runs automatically on public repos unless disabled
    label: "slop"   # Add a label to apply when slop is detected (no label applied by default)

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

Label flagged PRs

By default, Slop Detection does not apply any label, it only adds a note to the PR Walkthrough comment. To also apply a label to flagged PRs, set the label field:
.coderabbit.yaml
reviews:
  slop_detection:
    label: "slop"   # Or any label name you prefer, e.g. "ai-spam"

Frequently asked questions

No. Slop Detection only runs on public GitHub repositories.
No. Slop Detection does not block merges. When a PR is classified as slop, a note is added to the PR Walkthrough comment. If a label is configured, it is also applied so maintainers can filter and triage PRs at their discretion.
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