ai-slop-cleaner
Post-implementation cleanup that removes AI-generated bloat while preserving functionality. Runs pass-by-pass with test verification after each pass. Activate after kraken/spark complete a feature, or when a codebase needs hygiene work.
npx skills add vibeeval/vibecosystem --skill ai-slop-cleaner --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# AI Slop Cleaner AI code generation produces working code. It also produces unnecessary code alongside it. This skill removes the unnecessary parts while keeping everything that matters. ## What Is "AI Slop"? AI slop is code that: - Works, but shouldn't exist - Adds complexity without adding value - Was clearly generated to pad a response rather than solve a problem - Suggests the author wasn't thinking, just generating Common slop categories and their signals: | Category | Signal | |----------|--------| | Dead imports | Imported but never referenced in the file | | Unused variables | Declared, never read | | Commented-out code | Blocks of `// old code` or `/* removed */` | | Debug remnants | `console.log`, `print()`, `debugger`, `fmt.Println` | | Obvious comments | `// increment counter` above `count++` | | Redundant JSDoc | `@param name - the name` above `name: string` | | Premature abstractions | A factory that creates exactly one thing | | One-use helpers | Private function called exactly once, trivially inlinable | | Overly generic types | `<T extends object>` when `T` is always `User` | | Over-parameterized | `fn(a, b, c, d, e)` where 4 params never vary | | Unreachable bran
- What Is "AI Slop"?
- The Prime Directive
- Regression-Safe Workflow (Non-Negotiable)
- The 7 Cleaning Passes
- Pass 1: Dead Imports and Unused Variables
- Pass 2: Commented-Out Code and Debug Statements
- Pass 3: Obvious Comments and Redundant Documentation
- Pass 4: Dead Code (Unreachable Branches)
- Pass 5: Premature Abstractions (Inline One-Use Helpers)
- Pass 6: Duplication Consolidation
- Pass 7: Over-Engineering Simplification
- What Is Never Cleaned
- .slopignore File
- Metrics Report
What does the ai-slop-cleaner skill do?
Post-implementation cleanup that removes AI-generated bloat while preserving functionality. Runs pass-by-pass with test verification after each pass. Activate after kraken/spark complete a feature, or when a codebase needs hygiene work.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill ai-slop-cleaner --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.