deslopify
Skill1 starsChanged 2 months agoMITView on GitHub
Strip AI slop from code an agent just wrote — comments that restate the code, defensive branches for cases that can't happen, abstractions with one implementation, commented-out code, verbose docstrings on obvious functions. A diff-only pass that only ever removes or simplifies, never adds, so it can't introduce slop itself. Run after any agent session that touched code, before committing. Use when asked to "deslopify", "clean this up", "remove the slop", or as the last step before a commit.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- drinkspiller/skillstheir own version, first seen Nov 6, 2026
- iurysza/agent-skillstheir own version, first seen Nov 1, 2026
- kriscard/Skillstheir own version, first seen Oct 28, 2026
- display-design-studio/skillstheir own version, first seen Oct 6, 2026
- AdityaVasireddy/agent-skillstheir own version, first seen Sep 8, 2026
- sureshg/skillstheir own version, first seen Aug 7, 2026
Used with
Projects with it also use caveman and grill-me.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcaveman
Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 4 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- JuliusBrussee/skills★ 160same name
- kriscard/Skills★ 15same name
- AntonioSpagnol/UI-Deslopify-Skill★ 5same name
- iurysza/agent-skills★ 5same name
- AdityaVasireddy/agent-skills★ 2same name
- display-design-studio/skills★ 2same name
- shreyas-makes/agent-skills★ 2same name
- drinkspiller/skills★ 1same name
- sureshg/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bigquery-analyticsSkill
- cache-invalidationSkill
- mongo-aggregationSkill
- mongo-modelingSkill
- postgres-aggregationSkill
- postgres-indexingSkill
- redis-coordinationSkill
- redis-patternsSkill
- review-querySkill
- code-migrationSkill
- cut-releaseSkill
- data-migrationSkill
- deploy-serviceSkill
- hotfixSkill
- rollbackSkill
- design-endpointSkill
- design-eventSkill
- design-schemaSkill
- evolve-contractSkill
- scaffold-nestjs-moduleSkill
- scaffold-projectSkill
- incident-responseSkill
- investigate-bugSkill
- on-callSkill
- postmortemSkill
- audit-skillsSkill
- distill-review-styleSkill
- write-skillSkill
- debug-with-tracesSkill
- define-alertsSkill
- instrument-serviceSkill
- evaluate-dependencySkill
- grillSkill
- handoffSkill
- orientSkill
- phased-deliverySkill
- spikeSkill
- to-questionnaireSkill
- write-adrSkill
- write-prdSkill
- devops-pr-reviewSkill
- go-backend-pr-reviewSkill
- nestjs-backend-pr-reviewSkill
- python-backend-pr-reviewSkill
- react-frontend-pr-reviewSkill
- bisectSkill
- break-couplingSkill
- dead-code-sweepSkill
- extract-moduleSkill
- rebase-cleanSkill
- resolve-merge-conflictsSkill
- split-commitSkill
- tddSkill
- wait-whatSkill
- wide-renameSkill
- bullmqSkill
- kafkaSkill
- sqs-consumerSkill
- audit-dependenciesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Every edit in this pass removes or shortens.
- Distinctive: line 29
Delete. Keep a comment only if it explains *why*, records a non-obvious constraint, or warns about a footgun.
- Distinctive: line 40
Remove the guard. If the "impossible" case is actually reachable, that's a real bug — flag it, don't silently keep the guard.
- Very specific: line 55
Delete it. Git remembers. No "kept for reference", no // old: blocks.
- Very specific: line 81
Test names and it(...) strings that restate the assertion verbatim.
- Distinctive: line 99
If removing a guard breaks a test, decide: was the test asserting slop, or is the case real?
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deslopify
Agents pad. They narrate what the next line does, guard against inputs the type system already rules out, wrap one function in an interface "for testability", and leave the old version commented above the new one. This pass removes that.
Hard rule: subtractive only
Every edit in this pass removes or shortens. No new code, no new comments, no new abstractions, no renames, no behaviour changes. If a fix would add anything, it's out of scope for deslopify — note it and move on. This constraint is what keeps the pass from becoming another slop generator.
Work only from the diff of the session being cleaned (git diff, or the diff
against the branch point). Don't audit pre-existing code — that's not this pass.
What to cut
1. Comments that restate the code
// increment the counter
counter++Delete. Keep a comment only if it explains why, records a non-obvious constraint, or warns about a footgun. When unsure, the test is: does the comment survive the reader also reading the line below it?
2. Defensive code for cases that can't happen
- Null/undefined checks on a value the type guarantees is present.
default:branches on an exhaustive switch over a closed union.try/catcharound code that doesn't throw.- Re-validating an argument a caller one line up already validated.
if (!Array.isArray(x))on a parameter typedT[].
Remove the guard. If the "impossible" case is actually reachable, that's a real bug — flag it, don't silently keep the guard.
3. Abstractions with one implementation
- An
interface/Protocol/abstract classwith exactly one implementer and no test double that needs it. - A config object / options bag passed one value.
- A factory that constructs one type.
- A wrapper function that only forwards its arguments.
- A single-caller helper that's used once, three lines long, and named worse than the code it replaces.
Inline it back to the concrete thing.
4. Commented-out code
Delete it. Git remembers. No "kept for reference", no // old: blocks.
5. Verbose docstrings on obvious functions
def get_user_name(user):
"""
Get the name of the user.
Args:
user: The user to get the name of.
Returns:
The name of the user.
"""
return user.nameCut to one line, or delete if the signature already says everything. Keep docstrings that document units, edge-case behaviour, raised exceptions, or non-obvious contracts.
6. Other tells
- Redundant type annotations a good inferrer doesn't need (
const x: number = 5). console.log/print/logger.debugleft from the session.- Ceremonial blank lines and section-divider comments (
// ---- helpers ----) inside a short file. TODO/FIXMEwith no ticket and no owner that the session itself added.- Test names and
it(...)strings that restate the assertion verbatim. - Over-split functions: a function called once, whose body would read fine inlined.
What to leave alone
- Anything outside the session diff.
- Comments explaining why, TODOs that predate the session, domain-specific guards, docstrings carrying real contract detail.
- Style a formatter/linter owns — that's not slop, that's config.
- Genuine simplifications that require adding code (extract, dedupe, refactor) —
those belong in a separate
/simplifypass, not here.
Process
- Get the session diff. List the changed files.
- Walk each hunk against the six categories above.
- Apply only subtractive edits.
- Re-run the tests / typecheck / lint — a deslopify pass must leave them green. If removing a guard breaks a test, decide: was the test asserting slop, or is the case real? Real → revert and flag as a bug. Slop → the test goes too.
- Report: what was cut (grouped by category), and anything you flagged as a real
bug or a follow-up
/simplify.
Anti-patterns for the agent running this
- ❌ Adding a comment, a rename, or a refactor "while you're in there".
- ❌ Touching code the session didn't.
- ❌ Removing a guard for a case that's actually reachable.
- ❌ Deleting a
whycomment because it looks like awhatcomment — read it. - ❌ Turning this into a general code review. One job: cut what the session padded.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

