ai-slop-cleanerlisted

# AI Slop Cleaner Use this skill to clean AI-generated code slop without drifting scope or changing intended behavior. In OMC, this is the bounded cleanup workflow for code that works but feels bloated, repetitive, weakly tested, or over-abstracted. ## When to Use Use this skill when: - the user explicitly says `deslop`, `anti-slop`, or `AI slop` - the request is to clean up or refactor code that feels noisy, repetitive, or overly abstract - follow-up implementation left duplicate logic, dead code, wrapper layers, boundary leaks, or weak regression coverage - the user wants a reviewer-only anti-slop pass via `--review` - the goal is simplification and cleanup, not new feature delivery ## When Not to Use Do not use this skill when: - the task is mainly a new feature build or product change - the user wants a broad redesign instead of an incremental cleanup pass - the request is a generic refactor with no simplification or anti-slop intent - behavior is too unclear to protect with tests or a concrete verification plan ## OMC Execution Posture - Preserve behavior unless the user explicitly asks for behavior changes. - Lock behavior with focused regression tests first whenever practical. - Write a cleanup plan before editing code. - Prefer deletion over addition. - Reuse existing utilities and patterns before introducing new ones. - Avoid new dependencies unless the user explicitly requests them. - Keep diffs small, reversible, and smell-focused. - Stay concise and evidenc