Deslop
Strip AI-generated noise from your branch diff—extra comments, defensive try/catch, any casts, and off-style patterns—before you open a PR.
Overview
Deslop is an agent skill most often used in Ship (also Build) that removes AI-generated slop from the current branch diff against main before review or merge.
Install
npx skills add https://github.com/brianlovin/claude-config --skill deslopWhat is this skill?
- Diffs current branch against main to scope slop removal
- Targets redundant comments, abnormal defensive checks, any casts, and inconsistent local style
- Ends with a 1–3 sentence summary of changes only
- Designed to run after agent-assisted coding sessions
- 1–3 sentence change summary at end of run
Adoption & trust: 1.1k installs on skills.sh; 349 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Agent-written patches often add verbose comments, odd defensive code, and style inconsistencies that make PRs harder to trust and merge.
Who is it for?
Solo devs using Claude or similar agents who want a fast hygiene pass on a feature branch before opening a pull request.
Skip if: Replacing human or security review, refactoring unrelated legacy debt, or repos without a clear main comparison branch.
When should I use this skill?
After writing code on the current branch; when cleaning unnecessary comments, defensive checks, any casts, or inconsistent style from AI-generated patches.
What do I get? / Deliverables
The branch diff is cleaned to match house style with a short summary of what was removed, ready for PR or release review.
- Cleaned branch diff
- Brief summary of slop removed
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Final polish on a feature branch is canonical Ship review work immediately before merge or release. Review subphase covers diff hygiene and style alignment rather than automated test execution or security scanning.
Where it fits
After an agent implements an API endpoint, deslop removes extra logging comments before you continue the feature.
Clean UI component diffs that added redundant prop guards inconsistent with neighboring components.
Run immediately before opening a PR so reviewers see minimal, on-style changes.
How it compares
Branch diff cleanup for AI artifacts, not a linter config pack or full static-analysis skill.
Common Questions / FAQ
Who is deslop for?
Indie builders and small teams who frequently land AI-generated code and need a consistent pre-PR cleanup step.
When should I use deslop?
Use it after writing code on a branch—late Build or Ship review—when the diff feels noisy compared to the rest of the codebase.
Is deslop safe to install?
It instructs git diff and edits; review permissions and the Security Audits panel on this Prism page before installing from third-party config repos.
SKILL.md
READMESKILL.md - Deslop
# Remove AI code slop Check the diff against main, and remove all AI generated slop introduced in this branch. This includes: - Extra comments that a human wouldn't add or is inconsistent with the rest of the file - Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase (especially if called by trusted / validated codepaths) - Casts to any to get around type issues - Any other style that is inconsistent with the file Report at the end with only a 1-3 sentence summary of what you changed