Ai Slop Cleaner

This is a Hermes-native ai-slop-cleaner workflow skill.

Why This Exists

ai-slop-cleaner exists to keep maintenance work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.

Do Not Use When

• The goal is new or changed behavior rather than removing existing code; a plain refactor, feature, or fix request belongs to ulw-work.
• The cleanup would change architecture or module boundaries and needs its execution shaped into phases first; use omh-refactor-plan, or ulw-plan when the direction itself is still contested.
• The user wants code judged for bugs or merge readiness with no drafted slop removal to inspect; use omh-code-review for a bug-first review and omh-failure-signal-audit for swallowed failures.
• The user asks to simplify their own recent changes, a commit, or the staged diff with a reuse, quality, and efficiency pass rather than a behavior-locked removal of existing code; load Hermes' bundled simplify-code skill for that instead of this one.

Examples

Good example: