cleanup-list
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Run a comprehensive codebase cleanup audit and produce a detailed technical debt report — without modifying any code. Use this skill whenever a user wants to audit a codebase, identify dead code, find unused assets, surface technical debt, review dependencies, check for duplicate logic, or create a cleanup roadmap. Triggers include: "audit my codebase", "find dead code", "what can I delete", "cleanup report", "technical debt", "what's unused", "dependency review", "find duplicates in my code", "codebase health check", "what should I refactor", "find legacy code", "what can I remove safely", "cleanup roadmap", or any request to analyze a codebase for improvement opportunities — even if the user doesn't use these exact words. Always use this skill when the user shares a codebase and asks what can be simplified, removed, or improved.
In this repository16 other files it gives its agents.
- add-google-analyticsSkill
- brand-style-guideSkill
- codebase-cleanup-auditSkill
- code-reviewSkill
- copy-pricing-guideSkill
- figma-design-systemSkill
- improve-test-coverageSkill
- logo-prompt-generatorSkill
- maintain-code-dependenciesSkill
- organic-distribution-engineSkill
- performanceSkill
- product-blueprintSkill
- reddit-market-intelSkill
- security-reviewSkill
- seo-aeoSkill
- viral-image-prompt-generatorSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.