Skip to content

Guide · Agent skill

How to use the AI Slop Cleaner agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The AI Slop Cleaner is an agent skill from the oh-my-claudecode project that teaches an AI coding agent to tidy code an AI wrote. It targets code that works but is bloated, with duplicate logic, dead code, pass-through wrappers and weak tests. This guide explains what the skill makes the agent do, how to install it, how to trigger it with plain requests, and what to check before you rely on it.

AI Slop CleanerYeachan-Heo/oh-my-claudecode · MIT

Quick start

  1. 1Download and unzip the skill. Download the ai-slop-cleaner ZIP from this page and unzip it. The skill is a file named SKILL.md.
  2. 2Place it in a skills folder. Move the folder into ~/.claude/skills/ for personal use or into your project's .claude/skills/ folder. In the Claude apps, upload it under Settings → Capabilities → Skills instead.
  3. 3Make sure tests exist. Confirm your project has the test, lint and typecheck tooling the skill will run. The skill needs these to verify behavior.
  4. 4Name the target. Choose a bounded target, such as one module or a short list of changed files, and state that behavior must not change.
  5. 5Ask for the cleanup. Make a natural request such as deslop this module or cleanup the AI slop in a folder without changing behavior.
  6. 6Run a reviewer pass. Optionally add --review so a separate reviewer checks the changes without editing files.
  7. 7Read the report. Check changed files, simplifications, verification run and remaining risks before you accept the work.

What the AI Slop Cleaner skill makes the agent do

The skill sets a disciplined order of work for cleanup. The agent first identifies what must stay the same and adds or runs focused regression tests. It then writes a cleanup plan, classifies the problems it finds, and removes code in small, reversible passes. The skill says to prefer deletion over addition and to reuse existing utilities before adding new ones.

The skill sorts problems into six groups: duplication, dead code, needless abstraction, boundary violations, missing tests, and UI/design defaults. It runs one smell-focused pass at a time, for example dead code deletion first, then duplicate removal, then naming and error handling, then test reinforcement.

Install the skill from the ZIP or the Claude apps

Download the ZIP for the skill from this page and unzip it. The skill is a single file named SKILL.md. Place the unzipped skill folder in your personal skills directory at ~/.claude/skills/ so it is available across projects, or in a project's .claude/skills/ folder so it applies only to that project.

If you use the Claude apps instead, open Settings, go to Capabilities, and upload the skill under Skills.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ inside your project
  • Claude apps: Settings → Capabilities → Skills

Trigger the skill with natural requests

You can ask for the cleanup in ordinary language. The skill is meant for requests such as cleaning up or refactoring code that feels noisy, repetitive or overly abstract. Saying the words deslop, anti-slop or AI slop also signals the skill clearly.

You can also call it with the slash-style usage the source documents. Give it a target such as a module, or a list of files. Add --review to run a reviewer-only pass that checks work without editing files.

  • Good: deslop this module: too many wrappers, duplicate helpers, and dead code
  • Good: cleanup the AI slop in src/auth and tighten boundaries without changing behavior
  • Bad: refactor auth to support SSO
  • Bad: clean up formatting
/oh-my-claudecode:ai-slop-cleaner <target>

Use scoped file lists and review mode

Limiting the skill to specific files keeps the cleanup safe. You can pass a file list, for example skills/ralph/SKILL.md and skills/ai-slop-cleaner/SKILL.md. The skill is designed not to expand a changed-file scope into broader work unless you ask.

Review mode is a separate reviewer-only pass. The source says the reviewer should not start by editing files. It checks for leftover dead code, duplicate logic, needless wrappers, missing tests and cleanup that changed behavior without intent, then returns a verdict. Needed changes go back to a separate writer pass.

  • Standard run: /oh-my-claudecode:ai-slop-cleaner <file-a> <file-b> <file-c>
  • Reviewer-only run: add --review after the cleanup work is drafted
/oh-my-claudecode:ai-slop-cleaner <file-a> <file-b> <file-c> --review

Check the report the agent returns

The skill requires a final report with four parts. Read these before accepting the changes. The changed files list shows what was touched. Simplifications describes what was removed or consolidated. Behavior lock and verification run shows which tests, lint and typecheck were run. Remaining risks lists anything the agent could not protect.

  • Changed files
  • Simplifications
  • Behavior lock / verification run
  • Remaining risks

What people use it for

  • Removing duplicate helper functions that were copied across a module after an agent session.
  • Deleting unused exports, unreachable branches and leftover debug code from a feature branch.
  • Collapsing pass-through wrapper layers that add indirection without adding behavior.
  • Adding regression tests for behavior that works but has no coverage, before any edits.
  • Giving a reviewer a checklist for leftover dead code, duplication and missing tests after a cleanup.

Frequently asked questions

Is the AI Slop Cleaner skill free?

The skill is published under the MIT licence in the oh-my-claudecode repository. The source does not mention pricing, so check the licence file in the repository for the terms that apply.

What do I need to use the ai-slop-cleaner skill?

You need an agent runtime that can read the skill and edit project files. Your project also needs its own test, lint and typecheck tooling, because the skill runs the relevant ones. The skill runs no scripts and uses no network access, according to the source.

Where do I install the ai-slop-cleaner skill?

Unzip the downloaded ZIP into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, you can upload it under Settings → Capabilities → Skills.

What does the --review flag do?

The --review flag starts a reviewer-only pass. It checks cleanup plans, changed files and verification evidence for leftover dead code, duplication, needless wrappers and missing tests. It does not edit files and returns a verdict with follow-ups.

Will the skill add new features or change behavior?

No. The skill is designed to preserve behavior unless you explicitly ask for changes. It is not meant for new feature work, broad redesigns or generic refactors, and it says to avoid those tasks.

Can I use it for a broad redesign of my codebase?

The source says no. The workflow is designed for incremental, bounded cleanup. For broad redesigns, a different approach is needed, and the skill itself advises against using it for those.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you have AI-written code that runs but is cluttered, and you want a bounded, test-first cleanup limited to specific files. Skip it for new features, redesigns or code whose behavior you cannot protect with tests, since the skill itself refuses those jobs.

Download the skill