Ai Slop Cleaner

This is an OMH ai-slop-cleaner workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

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.

Examples

Good example:

• Prompt: $ai-slop-cleaner remove duplicated router branches and lock behavior with regression tests before refactoring.
• Expected behavior: Plan cleanup, preserve behavior, delete or simplify code, and prove it with targeted tests.
• Why: The request is maintenance cleanup with regression risk.

Bad example:

• Prompt: ai-slop-cleaner: treat casual chat or unaccepted work as if this workflow already produced verified results.
• Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing ai-slop-cleaner.
• Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.

Completion Checklist