| name | deslop |
| description | Remove AI-generated code slop from the current branch by auditing `git diff main...HEAD` and applying minimal cleanups. Use when a user asks to de-slop a PR/branch, make code look human-written, or remove over-defensive/verbose/generated patterns without changing behavior. |
De-Slop Diff
Workflow
- Run
git diff main...HEAD to inspect branch-only changes.
- Review each changed file against its local style and patterns.
- Remove only clear slop while preserving behavior and scope.
- Keep edits minimal and avoid unrelated refactors.
Remove These Patterns
- Decorative comment separators: remove divider comments like
# --------, // ========, and other visual filler.
- Self-evident/verbose comments: remove comments that merely narrate obvious code behavior.
- Redundant docstrings: remove docstrings that only restate the function/class name without useful detail.
- Type escape hatches: remove
any/Any workarounds when a concrete type is straightforward (prioritize TypeScript any).
- Overly verbose variable names: shorten names that are unnecessarily long while keeping clarity.
- Over-defensive code: remove abnormal guard clauses/try-catch blocks in trusted code paths.
- Style inconsistencies: align naming, formatting, and structure to nearby code.
- Unnecessary abstractions: inline one-off helpers that add indirection without reuse.
- Verbose error handling: remove catch/rethrow or logging-only catches that add no value.
Decision Rules
- Preserve behavior; de-slop is cleanup, not feature redesign.
- Preserve meaningful documentation (non-obvious rationale, constraints, API contracts, and caveats).
- Prefer the smallest possible diff that resolves the issue.
- If a pattern is ambiguous, leave it and note it rather than over-editing.
- Respect existing project conventions and lint/type constraints.
Output
After cleanup, report a 1-3 sentence summary of what changed.
If no slop is found, state that explicitly in 1 sentence.
