deslop
Skill0 starsChanged 9 months agoMITView on GitHub
Check the diff against main, and remove all AI generated slop introduced in this branch; keywords: deslop. Use only on explicit request; skip in routine implementation discussions.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 107 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Check the diff against main, and remove all AI generated slop introduced in this branch.
“Common” is measured: kept by at least 6 in 10 of the 107 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
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
Other versions108 projects use a version of this.
Word for word · 0
None found.
Edited · 23
- jaredpalmer/kev★ 9.3k13% same
- joe-bell/cva★ 6.9k11% same
- sanity-io/sanity★ 6.4k13% same
- bytemeadow/godot-bevy★ 56014% same
- brianlovin/claude-config★ 37677% same
- Scino/fstack★ 1813% same
- mariusflorescu/pstack-t3★ 1313% same
- Stormix/transcripts-mcp★ 870% same
- jamesblackwell/falcondeck★ 717% same
- cogine-ai/cogine-dev-skillset★ 413% same
13 more not listed
Wrote their own version · 85
- molt-bot/clawdbot★ 391ksame name
- every-app/open-seo★ 26ksame name
- millionco/react-doctor★ 15ksame name
- millionco/expect★ 3.6ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- compozy/compozy★ 2.8ksame name
- Jwuthri/Tracely-ai★ 1.5ksame name
- jwuthri-cloud/Tracely-ai★ 1.2ksame name
- pedronauck/skills★ 641same name
- friuns2/openclaw-android-assistant★ 556same name
75 more not listed
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.
Used alongsideProjects with it also use control-cli, verify-this and 10 more.
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.
AnastasiyaWSkillcontrol-cli
Drive and inspect an interactive CLI or TUI with a repeatable local harness, deterministic input, transcripts, and optional profiling. Use for CLI UX checks, prompt flows, startup regressions, hangs, interrupts, resize behavior, or memory growth. Do not use for a non-interactive command that a normal test can cover.
Also in 6 projects that use this
AnastasiyaWSkillverify-this
Prove a concrete behavior, performance, UI, CLI, API, or memory claim with fresh baseline-versus-treatment evidence and one explicit verdict. Use when asked to verify, prove, compare before and after, show evidence, or confirm that a fix works. Do not use for vague claims such as cleaner code, a full plan-based release verification, or a known bug that needs a red-to-green reproducer.
Also in 6 projects that use this
JwuthriSkillsimple-issue-description
Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior. Use when a contributor asks to simplify an issue, explain what a PR is for, create the corresponding issue for a PR, remove implementation detail from a report, or invokes /simple-issue-description.
Also in 3 projects that use this
JwuthriSkillopenseo-review-web-content
Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.
Also in 3 projects that use this
jaydubya818Skillprinciple-attack-the-premise
Apply when repeated fixes fail and a shared assumption may be wrong.
Also in 5 projects that use this
jaydubya818Skillprinciple-test-behavior-not-implementation
Apply when tests mirror internals instead of asserting observable outcomes.
Also in 5 projects that use this
- +1 more from AnastasiyaW
- +2 more from Jwuthri
- +1 more from jaydubya818
In this repository31 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- clarify-taskSkill
- code-reviewSkill
- create-prSkill
- database-migrationSkill
- debug-issueSkill
- diagramsSkill
- docker-logsSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- generate-api-docsSkill
- generate-pr-descriptionSkill
- git-commitSkill
- git-pushSkill
- light-review-existing-diffsSkill
- lint-fixSkill
- lint-suiteSkill
- onboard-new-developerSkill
- optimize-performanceSkill
- overviewSkill
- refactor-codeSkill
- roadmapSkill
- run-all-tests-and-fixSkill
- security-auditSkill
- security-reviewSkill
- setup-new-featureSkill
- visualizeSkill
- write-unit-testsSkill
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.

