codebase-cleanup-audit
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Produce a comprehensive, read-only technical-debt and cleanup audit of a codebase — dead code, duplicate logic, legacy features, architectural issues, unused dependencies, database cruft, and security risks — delivered as a structured Markdown report with per-item confidence/risk ratings and a phased cleanup roadmap. Use this skill whenever the user wants to clean up, audit, or analyze a codebase for technical debt, asks "what can I safely delete", or mentions dead/unused code, unused dependencies, unused exports or imports, duplicate utilities, legacy or deprecated code paths, refactoring opportunities, code reduction, or wants a cleanup plan or roadmap — even if they never say the word "audit". The skill NEVER modifies, patches, or deletes code; it only reports. It traces dynamic imports, route and DI registrations, reflection, framework conventions, and config references before flagging anything, so it is the right tool any time accuracy about what is actually unused matters.
In this repository16 other files it gives its agents.
- add-google-analyticsSkill
- brand-style-guideSkill
- cleanup-listSkill
- 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
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
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.