deslop
Deslop
Remove AI-generated code patterns from all changes in the current branch.
Process
- Run
git diff mainto get all changes - For each changed file, read the full file to understand existing style
- Identify and remove slop patterns (see below), matching the file's existing style
- Report a 1-3 sentence summary of changes
Slop Patterns
Remove these when inconsistent with the surrounding code:
- Unnecessary comments - Comments a human wouldn't add or that don't match the file's commenting style
- Defensive overkill - Extra try/catch blocks, null checks, or validation that's abnormal for that area (especially on trusted/validated codepaths)
- Type escape hatches - Casts to
anyto bypass type issues - Single-use variables - Variables used once immediately after declaration; inline the RHS instead
- React prop interfaces - Separate
interface Propsdefinitions; inline the props type directly - Style drift - Any formatting, naming, or patterns inconsistent with the file
Style Matching
Before editing, study the unchanged code in each file:
- Comment density and style
- Error handling patterns
- Variable naming conventions
- Type annotation style
- Component patterns (for React)
Only flag something as slop if it deviates from the file's established patterns.
Output
End with only a 1-3 sentence summary of what was changed. No detailed lists.
More from ilamanov/skills
spec-builder
Transform vague product or feature ideas into concrete, detailed specification documents through an interactive interview process. Use when the user wants to flesh out an idea, create a spec, write requirements, plan a product/feature/prototype, or go from "I have this idea..." to a concrete document. Works for software products, physical products, services, or any concept that needs specification.
23pr
Commit changes and create or update a pull request following project standards. Use when the user wants to commit work, create a PR, update an existing PR, or use the /pr command.
14reimplement-branch
Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when the user wants to clean up messy commits, create a tutorial-style commit history, or prepare a branch for review with logical, self-contained commits. Triggers on requests like "clean up my commits", "reimplement this branch", "create a clean history", or "make my commits reviewable".
12compile-conversation-into-doc
Turn long, messy AI chat conversations into clear, durable, and easily scannable reference documents that humans can reliably return to weeks or months later.
9review-bug-fixer
Fix valid code review findings from one or more review markdown files. Use when the user has review files (e.g., review1.md, review2.md) containing code review findings, issues, or suggestions and wants to fix the valid ones in the current branch. Triggers on requests like "fix review findings", "fix issues from review", "apply code review fixes", or any mention of fixing bugs/issues from review markdown files.
8incremental-plan
Break a product or feature spec into a sequence of small, independently testable implementation steps. Use when the user has a spec document and wants to implement it incrementally rather than all at once — building and verifying one piece at a time before moving on. Triggers on requests like "break this spec into steps", "create an incremental plan", "split this into parts I can test", "how should I implement this step by step", "create a build plan", or when a user has a spec and wants a phased implementation approach.
6