code-cleanup
Skill1 starsChanged 23 days agoApache-2.0View on GitHub
Simplify requested code or active changes while preserving behavior.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- edloidas/skillstheir own version, first seen Nov 1, 2026
- snappedly/skillstheir own version, first seen Oct 13, 2026
- CorySchulz/skillstheir own version, first seen Oct 13, 2026
- hempq/symfony-claude-codetheir own version, first seen Oct 9, 2026
- looties-io/looties-skillstheir own version, first seen Sep 24, 2026
- evanpersinger/claude-skillstheir own version, first seen Aug 16, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- jenreh/appkit★ 4same name
- CorySchulz/skills★ 2same name
- edloidas/skills★ 2same name
- snappedly/skills★ 2same name
- hempq/symfony-claude-code★ 1same name
- looties-io/looties-skills★ 1same name
- evanpersinger/claude-skills★ 0same name
- szmidtpiotr/ClaudeCode-Tools★ 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-testSkill
- audit-fixissuesSkill
- autoresearchSkill
- benchmark-optimizeSkill
- circleci-job-resultsSkill
- citation-verifierSkill
- cli-designSkill
- codebase-auditSkill
- deep-code-cleanupSkill
- doc-updateSkill
- emendSkill
- fix-issueSkill
- git-github-workflowSkill
- goal-modeSkill
- inspect-datasetSkill
- manage-pr-lifecycleSkill
- medcognetics-brandSkill
- notify-wakeSkill
- repo-maintenanceSkill
- review-fix-loopSkill
- standardize-ciSkill
- token-file-authSkill
- whats-nextSkill
- yeetSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
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 12
Remove duplication, dead code, redundant checks, and comments that obscure the code.
- Distinctive: line 20
Use characterization tests before refactoring weakly covered logic.
- Distinctive: line 24
Run affected tests and repository gates.
“Common” is measured: kept by at least 6 in 10 of the 8 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
Code Cleanup
Accept $code-cleanup with optional paths or functions. Use explicit targets
first, then changed files. With neither, select a concrete maintenance problem
with low behavior risk. Use $deep-code-cleanup for a requested exhaustive pass.
Remove duplication, dead code, redundant checks, and comments that obscure the code. Prefer existing utilities and direct control flow. Introduce helpers only when they clarify responsibility or remove meaningful repetition.
Preserve runtime behavior and public interfaces within the cleanup scope. Continue safe improvements while reporting changes that need a new behavior or design decision. Do not ask again for a change already authorized by the task.
Use characterization tests before refactoring weakly covered logic. They should pass on the baseline. For a reproducible bug within the authorized scope, confirm a failing regression before the fix.
Run affected tests and repository gates. Finish when the selected cleanup is complete and validated. Report what became simpler, why behavior is preserved, and unresolved risks. Include line counts only when they help explain the result.
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.