AI Slop Cleaner
Regression-safe, deletion-first code cleanup skill (oh-my-claudecode) — deslop modules without changing behavior, with optional reviewer-only mode.
Overview
AI Slop Cleaner lives in yeachan-heo/oh-my-claudecode. It is the bounded cleanup workflow for code that works but feels bloated, repetitive, weakly tested, or over-abstracted. Workflow: lock behavior with tests, write a cleanup plan, classify smells (duplication, dead code, needless abstraction, boundary violations, missing tests, UI defaults), then run smell-focused passes. Supports `--review` for writer/reviewer separation and Ralph integration for post-session cleanup on changed files only.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
npx skills add yeachan-heo/oh-my-claudecodeInvoke as `/oh-my-claudecode:ai-slop-cleaner` (optional `--review`). Source skill folder: `skills/ai-slop-cleaner`.
How to use it
1. Point at a module or changed-file list. 2. Let it lock behavior / state a verification plan. 3. Run deletion-first passes (dead code → duplicates → naming → tests). 4. Use `--review` for a separate reviewer verdict. 5. Do not use for feature builds or broad redesigns.
Example prompts
- “deslop this module: too many wrappers, duplicate helpers, and dead code”
- “/oh-my-claudecode:ai-slop-cleaner src/auth -- keep behavior identical”
- “/oh-my-claudecode:ai-slop-cleaner --review on the cleanup plan for src/billing”
- “Clean AI slop in the files changed this session; do not expand scope.”
Use cases and examples
- Deslop a module full of wrappers and duplicate helpers
- Post-Ralph cleanup on session-changed files only
- Reviewer-only anti-slop pass before merge
- Tighten boundaries without changing behavior
- Clean AI-generated React UI defaults that feel unreviewed
Prerequisites
- Test runner or clear verification plan for the touched area
- Claude Code with oh-my-claudecode skills installed
- Explicit anti-slop / simplify intent (not a vague “refactor”)
Tips
- Prefer deletion over addition; reuse existing utilities first.
- Keep diffs small and reversible.
- UI checklist flags default blue/purple palettes and uniform 3-column grids when unjustified.
- Pair with code-simplifier / simplify for complementary cleanup styles.