deslop
Skill0 starsChanged 17 days agoMITView on GitHub
Load before git commit, git push, opening a PR, or reporting a code change complete. Load it even if you think you know it; the file is the source of truth. Remove AI-generated code slop from the branch diff: comments that restate the line, defensive checks on trusted paths, `any` casts, deep nesting, and patterns that disagree with the surrounding file. Apply it even when the user did not mention slop or style. Also load when the user says 提交 / 推送 / 开 PR / 清理分支 / 清理 AI 生成的代码 / 去掉多余注释 / 代码去噪 / 简化嵌套 / 清理防御性检查. Not for prose (use unslop), architecture decisions, or behavior changes.
- Commits and pushes
118 other projects use a version of this, 30 of them edited.
Adopted by
Most recently taken up by
- lalulali/vespyrtheir own version, first seen Nov 8, 2026
- ferologics/pi-skillstheir own version, first seen Nov 8, 2026
- novuhq/novuedited, first seen Nov 8, 2026
- openclaw/openclaw-enterprisetheir own version, first seen Nov 8, 2026
- ADWilkinson/astacktheir own version, first seen Nov 8, 2026
- MammadovEshgin/clean-code-skilltheir own version, first seen Nov 8, 2026
Used with
Projects with it also use simple-issue-description, control-cli 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.
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 4 projects that use this
ElyzeSolutionsSkillcontrol-cli
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
Also in 6 projects that use this
- JwuthriSkill
openseo-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 4 projects that use this
learnerLjSkillverify-this
Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
Also in 6 projects that use this
- ElyzeSolutionsSkill
control-ui
Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.
Also in 7 projects that use this
ten9876Skillpapercuts
Read-only AetherSDR issue triage that surfaces the UX papercuts, bugs, and regressions you can fix AND prove today with the agent automation bridge. Use when the user says $papercuts or /papercuts, or asks to "find papercuts", "what can I fix and prove today", "triage bridge-provable issues", "what UX bugs can the bridge close", "sort issues by priority I can knock out", or otherwise wants a curated, lifecycle-aware (design→code→prove) shortlist of issues — NOT the label-and-respond /triage workflow. This is the discovery step that feeds /fb. Strictly read-only: it never labels, comments, closes, or edits issues.
Also in 4 projects that use this
- +5 more from Jwuthri
Other versions118 projects use a version of this.
Word for word · 0
None found.
Edited · 30
- novuhq/novu★ 40k64% same
- jaredpalmer/kev★ 9.8k88% same
- joe-bell/cva★ 6.9k75% same
- sanity-io/sanity★ 6.4k88% same
- bytemeadow/godot-bevy★ 57590% same
- brianlovin/claude-config★ 37615% same
- zvadaadam/az-skills★ 5036% same
- ulises-jeremias/agent-toolkit★ 1953% same
- Scino/fstack★ 1883% same
- mariusflorescu/pstack-t3★ 1388% same
20 more not listed
Wrote their own version · 88
- molt-bot/clawdbot★ 391ksame name
- every-app/open-seo★ 27ksame name
- millionco/react-doctor★ 15ksame name
- millionco/expect★ 3.6ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- compozy/compozy★ 2.9ksame name
- Jwuthri/Tracely-ai★ 1.3ksame name
- jwuthri-cloud/Tracely-ai★ 979same name
- pedronauck/skills★ 649same name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
78 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.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-ablationSkill
- benchmark-checklistSkill
- blast-radiusSkill
- codebase-designSkill
- correctSkill
- create-verification-skillSkill
- design-practiceSkill
- external-agent-handoffSkill
- howSkill
- nuclear-reviewSkill
- reflectSkill
- sharpenSkill
- tddSkill
- tech-diagramsSkill
- technical-writingSkill
- unslopSkill
- web-craftSkill
- whySkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 116 edited versions we read keep these.
4
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 16
Check the diff against main and remove AI-generated slop introduced in the branch.
- Distinctive: line 28
Keep behavior unchanged unless fixing a clear bug.
- Distinctive: line 29
Prefer minimal, focused edits over broad rewrites.
- Distinctive: line 30
Keep the final summary concise (1-3 sentences).
“Common” is measured: kept by at least 6 in 10 of the 116 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 AI-generated slop introduced in the branch.
Focus Areas
- Extra comments that are unnecessary or inconsistent with local style
- Defensive checks or try/catch blocks that are abnormal for trusted code paths
- Casts to
anyused only to bypass type issues - Deeply nested code that should be simplified with early returns
- Other patterns inconsistent with the file and surrounding codebase
Guardrails
- Keep behavior unchanged unless fixing a clear bug.
- Prefer minimal, focused edits over broad rewrites.
- Keep the final summary concise (1-3 sentences).
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.