clean
Skill207 starsChanged 4 months agoMITView on GitHub
Polish your own diff by hand with KISS/DRY and local style — the pre-handoff pass, not a test run and not a subagent sweep. Use for /clean, "clean it up", "tidy this", and automatically before creating, updating, or automerging a PR or moving to the next one.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- hemal08ce094/DesignSkillsSwiftUItheir own version, first seen Nov 8, 2026
- Mrbaeksang/skillstheir own version, first seen Nov 8, 2026
- cekrauseee/harnesstheir own version, first seen Nov 1, 2026
- snuffish/dotfilestheir own version, first seen Nov 1, 2026
- mystilleef/spae-frameworktheir own version, first seen Oct 28, 2026
- flavien-ia/hypervibe-crafttheir own version, first seen Oct 25, 2026
Used with
Projects with it also use expressive, friendly 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.
bergsideSkillexpressive
Vibrant, personality-driven design with bold colors, playful graphics, and dynamic layouts that balance creativity with structure.
Also in 4 projects that use this
- bergsideSkill
friendly
Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel color palettes.
Also in 4 projects that use this
- +10 more from bergside
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- bergside/awesome-design-skills★ 2.9ksame name
- aimeos/pagible★ 602same name
- kurtosis-tech/kurtosis★ 558same name
- flavien-ia/hypervibe-craft★ 50same name
- flavien-ia/hypervibe-harness★ 50same name
- RektTillNoon/alpha-skills★ 4same name
- VoTruongDanh/Skills-Agent★ 4same name
- andalabx/skills★ 2same name
- mystilleef/spae-framework★ 2same name
- Mrbaeksang/skills★ 1same name
8 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 repository22 other files it gives its agents.
- audit-onlySkill
- babysitSkill
- cprSkill
- draft-tweetSkill
- engraved-figuresSkill
- free-disk-spaceSkill
- list-open-workSkill
- notarize-macSkill
- no-tropesSkill
- perfSkill
- pr-readySkill
- pr-triageSkill
- pr-updateSkill
- researchSkill
- runtime-debugSkill
- stacked-prSkill
- ticket-shipSkill
- triageSkill
- ui-onlySkill
- ui-systemSkill
- visual-verifySkill
- workSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
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 29
Prefer the small sharp version over ceremony.
- Distinctive: line 38
Run the test suite / tsc / lint just because you were told to "clean"
“Common” is measured: kept by at least 6 in 10 of the 16 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
Clean
KISS/DRY and copy the local code style. Be elitist, shorthand, clever, concise, efficient, and elegant.
"Clean" means polishing the code — it does NOT mean running the test suite, tsc, or lint as the task. Run a check only if it's genuinely needed to confirm the polish is safe.
Clean is a standalone pass, not just a pre-PR step — run it whenever things get messy, including mid-work. Also run it automatically before any PR handoff (creating, updating, automerging, or moving to the next PR) without being told each time.
Do
- Re-read your diff. Cut dead code, leftover debug logging, and duplication.
- Extend existing helpers — don't parallel-implement.
- Match neighboring style (names, imports, file layout, comment density).
- Prefer the small sharp version over ceremony.
- UI work: only after they like the UI (
ui-only). Useui-systemfor primitives. - On the PR: title/body describe the change as a whole (a short intro), not a
changelog of steps. Split into topical commits (
pr-update), runno-tropeson the text, and link the PR.
Don't
- Run the test suite / tsc / lint just because you were told to "clean"
- Unrelated refactors
- New abstractions with one caller
- Scope creep dressed up as cleanup
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.