remove-ai-slops
Remove AI-generated code smells (slop) from branch changes or an explicit file list. Locks behavior with regression tests FIRST, then runs categorized cleanup via parallel `deep` agents in batches of 5, then verifies with quality gates. Covers 10 slop categories including performance equivalences, excessive complexity (object annotations, if/elif variant chains), and oversized modules (250+ pure LOC with mandatory modular refactoring). MUST USE when the user asks to \"remove slop\", \"clean AI code\", \"deslop\", \"clean up AI-generated code\", \"remove AI slop\", or wants to clean up AI-gener
Profile →npx skills add code-yeongyu/oh-my-openagent --skill remove-ai-slops --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.
# Remove AI Slops Skill ## Inputs - **Default scope**: branch diff vs `merge-base main` (no arguments needed) - **Optional scope**: explicit file list passed by the caller (e.g., a Ralph workflow's changed-files set) ## What this skill does Cleans AI-generated slop from a bounded set of changed files while strictly preserving behavior. Locks behavior with regression tests first, then runs a categorized multi-pass cleanup, then verifies with quality gates and a critical review. Reverts and direct-edits when verification fails. The core safety invariant: **behavior is locked by green tests before a single line is removed**. A checklist alone is not safety; a passing regression test is. --- ## Categories (what counts as slop) The agent looks for these nine categories. The first three are stylistic, the next three are structural, the next two are about hidden cost, and the last is about behavior coverage. ### Stylistic 1. **Obvious comments** — comments restating code, trivial docstrings, section dividers, commented-out code, vague TODOs/Notes. - KEEP: comments explaining WHY (business logic, edge cases, workarounds), ticket links, regex/algorithm explanations. - KEEP: BDD markers (`#
- Inputs
- What this skill does
- Categories (what counts as slop)
- Stylistic
- Structural
- Hidden cost
- Behavior coverage
- Quality Gates
- Process
- Phase 0: Plan with TodoWrite
- Phase 1: Determine scope
- Phase 2: Lock behavior with regression tests (NEW — non-negotiable)
- Phase 3: Cleanup plan — existence first, then smells
- Phase 4: Parallel slop removal via deep agents in batches of 5
git diff $(git merge-base main HEAD)..HEAD --name-only
What does the remove-ai-slops skill do?
Remove AI-generated code smells (slop) from branch changes or an explicit file list. Locks behavior with regression tests FIRST, then runs categorized cleanup via parallel `deep` agents in batches of 5, then verifies with quality gates. Covers 10 slop categories including performance equivalences, excessive complexity (object annotations, if/elif variant chains), and oversized modules (250+ pure LOC with mandatory modular refactoring). MUST USE when the user asks to \"remove slop\", \"clean AI code\", \"deslop\", \"clean up AI-generated code\", \"remove AI slop\", or wants to clean up AI-gener
How do I install it?
Run `npx skills add code-yeongyu/oh-my-openagent --skill remove-ai-slops --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 code-yeongyu/oh-my-openagent, a repository with 67,209 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.