← ClaudeAtlas

remove-ai-slopslisted

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-generated patterns from recent changes. Triggers - "remove ai slops", "clean ai code", "deslop", "cleanup AI generated", "remove AI slop", "clean up AI-generated code", "strip slop", "ai-slop cleanup".
code-yeongyu/oh-my-openagent · ★ 60,341 · AI & Automation · score 83
Install: claude install-skill code-yeongyu/oh-my-openagent
# 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 (`# given`, `# when`, `# then`, `# when/then`). 2. **Over-defensive code** — null checks for guaranteed values, try/except around code that cannot raise, isinstance checks for statically typed params, default values for required params, backward-compat shims, redundant validation duplica