unslop

Detect AI-generated slop in code, comments, and UI text.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill unslop-bradliebs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unslop
Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.github/skills/unslop
Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill unslop-bradliebs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified de-slop passes detect and report AI-generated "slop" — generic, template-looking, and overly enthusiastic output that degrades code quality, comments, and UI text.

Core Features & Use Cases

  • Three parallel passes (Code Slop, Comment Rot, Design Slop) identify issues in code, prose comments, and UI copy.
  • Returns structured findings to guide targeted cleanups before PRs, reviews, or releases.
  • Suitable for post-feature hygiene, pre-PR audits, and periodic codebase maintenance.

Quick Start

Run the unslop skill on a codebase to de-slop the latest changes

Frequently Asked Questions about unslop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect and clean AI-generated slop from my codebase before a pull request?

AI-generated slop is identified through a three-pass analysis workflow that scans code, comments, and UI text to find generic, template-looking, and overly enthusiastic output, returning structured findings to guide targeted cleanups.

What is comment rot and how does static analysis find it in AI-generated code?

Comment rot is generic, overly enthusiastic AI-generated prose in code comments. A dedicated static analysis pass identifies this template-looking text and returns structured findings to help you improve code quality before reviews.

Can I run a de-slop audit on specific files and directories changed in a commit?

Yes, the de-slop analysis applies to changes across specific files and directories, including commits, pull requests, and changed baselines, returning structured findings for code slop, comment rot, and design slop.

What is the best way to audit UI text and code quality for generic AI output?

The best way to audit for generic AI output is a parallel three-pass analysis covering Code Slop, Comment Rot, and Design Slop. This identifies template-looking UI text and code issues, returning structured findings to guide codebase maintenance.

When should I run a code review for AI-generated design slop during development?

You should run a code review for AI-generated design slop during post-feature hygiene, pre-PR audits, or periodic codebase maintenance to catch generic UI text and template-looking code before releases.