Technical Deslop

Purpose

When to use

• A diff feels over-explained, overly defensive, or inconsistent with surrounding code.
• You need a final cleanup pass before review/PR.
• You want to normalize style after automated generation.

Workflow

1. Capture scope with

   git diff --cached

   and

   git diff $(git merge-base origin/main HEAD)..HEAD

   .
2. Focus only on changed hunks (or user-scoped files).
3. Apply the cleanup sequence in

   references/playbook.md

   .
4. Remove slop patterns: redundant comments, unnecessary defensive branches, non-idiomatic casts, and style drift.
5. Re-check behavior boundaries: no logic changes unless the user explicitly requested them.
6. Report a short 1-3 sentence summary of cleanup performed.

references/slop-patterns.md

references/playbook.md

Inputs

• Optional file scope (

  FILES

  ) or explicit user file targets.
• Current branch diff and staged diff.
• Repository conventions from local instructions/config.

Outputs

• Behavior-preserving cleanup in touched files.
• Minimal summary of what was normalized and where.