ai-slop-cleaner

• The user explicitly says "deslop", "anti-slop", or "AI slop"
• The request is to clean up or refactor code that feels bloated, repetitive, or overly abstract
• The user wants a reviewer-only anti-slop pass via

  --review

  after cleanup work is drafted
• The user calls out duplicate code, dead code, wrapper layers, boundary violations, or weak regression coverage
• The goal is simplification, deletion, and cleanup rather than adding new features </Use_When>

• The task is primarily a new feature build -- use

  autopilot

  or direct implementation instead
• The user wants a broad architecture redesign rather than an incremental cleanup pass
• The request is a generic refactor with no cleanup/simplification intent
• Behavior is unclear and there are no tests or concrete anchors -- clarify scope first </Do_Not_Use_When>

Review Mode (

--review

)

--review

• Writer pass: make the cleanup changes with behavior locked by tests.
• Reviewer pass (

  --review

  ): inspect the result for duplication, dead code, boundary violations, missing tests, and unnecessary abstractions.
• The same pass must not both write and self-approve without a separate review step.

1. Do not make edits first.
2. Inspect the cleanup plan, changed files, and regression coverage.
3. Check specifically for:
   • leftover dead code or unused exports
   • duplicate logic that was not consolidated
   • needless wrappers or abstractions that still blur boundaries
   • missing tests or weak verification for preserved behavior
   • risky cleanup that changed behavior without explicit intent
4. Produce a reviewer verdict with required follow-ups.
5. If changes are needed, hand them back to a separate writer/executor pass instead of fixing and approving in one pass.

• Preserve behavior unless the user explicitly asks for behavior changes
• Lock behavior with regression tests first whenever practical
• Write a cleanup plan before editing code
• Prefer deletion over addition
• Reuse existing utilities and patterns before introducing anything new
• Avoid new dependencies unless the user explicitly requests them
• Keep diffs small, reversible, and smell-focused
• Keep writer/reviewer separation: author in one pass, review in another
• Verify with lint/typecheck/tests/static analysis relevant to the touched area </Execution_Policy>

1. Create a cleanup plan
   • Do not start coding immediately
   • List the targeted smells and the files likely involved
   • Sequence cleanup passes from lowest-risk deletion to higher-risk consolidation
2. Categorize the slop
   • Duplicate code
   • Dead or unused code
   • Needless abstraction / wrapper layers
   • Boundary violations / misplaced responsibilities
   • Missing or weak tests
3. Execute one smell-focused pass at a time
   • Pass 1: Dead code deletion -- remove unused branches, helpers, exports, and stale comments
   • Pass 2: Duplicate removal -- consolidate repeated logic into existing patterns where possible
   • Pass 3: Naming and error-handling cleanup -- tighten naming, trim noisy plumbing, normalize obvious inconsistencies
   • Pass 4: Test reinforcement -- fill any regression gaps revealed by the cleanup
4. Run quality gates
   • Run the relevant lint, typecheck, unit/integration tests, and any static or security checks already present for the touched area
   • If a gate fails, fix the underlying issue or revert the risky cleanup instead of forcing it through
5. Optional

   --review

   pass
   • Run a distinct reviewer pass that checks duplication, dead code, boundary violations, test coverage, and needless abstractions
   • If the reviewer finds issues, address them in a follow-up cleanup pass before closing the task
6. Report outcome
   • Changed files
   • Simplifications made
   • Behavior locked by tests
   • Remaining risks or slop intentionally left for a later pass </Steps>

• Changed files
• Simplifications
• Verification run
• Remaining risks </Final_Report>