Deslop
- 552 installs
- 356 repo stars
- Updated March 25, 2026
- brianlovin/agent-config
This is a copy of deslop by brianlovin - installs and ranking accrue to the original listing.
Deslop is a code-review skill that diffs the current branch against main and strips AI-generated slop—redundant comments, abnormal defensive checks, and any casts—for developers who want cleaner PRs before review.
About
Deslop is an agent-config skill that compares the current feature branch to main and removes AI-generated code slop introduced in that branch. It targets extra comments a human would not write, defensive try/catch blocks abnormal for trusted call paths, casts to any that bypass type errors, and style inconsistent with the rest of each file. After cleanup, Deslop reports a 1–3 sentence summary of what changed. Developers reach for Deslop after agent-assisted coding sessions and before opening or updating a pull request, when diffs look verbose or stylistically off compared to the existing codebase.
- Scans the current branch diff against main
- Removes extra comments, abnormal defensive checks, any-to-any casts, and style inconsistencies
- Outputs only a 1-3 sentence summary of changes made
- Hard-gate: run after code generation and before code review or merge
Deslop by the numbers
- 552 all-time installs (skills.sh)
- Data as of Aug 1, 2026 (Skillselion catalog sync)
npx skills add https://github.com/brianlovin/agent-config --skill deslopAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 552 |
|---|---|
| repo stars | ★ 356 |
| Last updated | March 25, 2026 |
| Repository | brianlovin/agent-config ↗ |
How do you clean AI slop from a branch?
Automatically clean AI-generated code artifacts like excessive comments, defensive checks, and type casts from a feature branch before review or merge.
Who is it for?
Developers who used AI coding agents on a feature branch and need a fast pre-PR pass to match existing codebase style.
Skip if: Developers who need functional bug fixes, security audits, or lint-rule enforcement rather than AI artifact cleanup on a branch diff.
When should I use this skill?
User finished AI-assisted coding on a branch and wants slop removed before review, merge, or opening a PR.
What you get
A cleaned branch diff, removed slop patterns, and a 1–3 sentence cleanup summary.
- Cleaned branch diff
- Slop removal summary
By the numbers
- Produces a 1–3 sentence cleanup summary after each run
Files
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
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kHow it compares
Use Deslop for fast AI artifact removal on branch diffs; use linters or dedicated review skills when you need rule-based enforcement or security findings.
FAQ
What slop patterns does deslop remove?
Deslop removes extra comments inconsistent with the file, abnormal defensive try/catch in trusted paths, casts to any for type bypasses, and other style that diverges from surrounding code. It only changes lines introduced on the current branch versus main.
When should deslop run in a workflow?
Deslop should run after AI-assisted coding on a feature branch and before code review or merge. The skill diffs against main, cleans introduced slop, then outputs a brief 1–3 sentence summary of edits made.