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 automatically applies a label (default: slop) so maintainers can filter and prioritize their review queue. 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"   # Optional — custom label to apply

​
Disabling Slop Detection

To disable Slop Detection on a repository, set enabled to false:
.coderabbit.yaml
reviews:
  slop_detection:
    enabled: false

​
Custom label

To use a different label for flagged PRs, set the label field:
.coderabbit.yaml
reviews:
  slop_detection:
    label: "ai-spam"

​
Frequently asked questions

No. Slop Detection only runs on public GitHub repositories.
No. Slop Detection applies a label to the PR but does not block merges. Maintainers can use the label to 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