component-cleanup
Skill192 starsChanged 6 days agoMITView on GitHub
Clean unused components, abandoned generated UI, and code or assets left behind by component migration. Inspect unimported component candidates and remove verified unused implementations and their exclusive support files; excludes general codebase, dependency-upgrade, or production-data cleanup.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- component-auditorSkill
- component-builderSkill
- component-inventorySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the component cleanup workflow.
- Very specific: line 14
Use audit-only when requested.
≈ “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.
Files
Component Cleanup
Read the component cleanup workflow. Target unused components, abandoned generated variants, replaced wrappers, and their exclusive styles, helpers, tests, exports and assets. Do not expand into unrelated application code or blanket dependency cleanup.
Include components with no imports in the candidate inventory. Before deletion, check dynamic registries, framework entry conventions, public package exports, content references and the project's explicitly retained base library. No imports is a discovery signal, not deletion proof.
Use audit-only when requested; otherwise implement authorized cleanup in small verified batches. Keep unresolvable candidates and explain the missing evidence. Refresh the existing component system document and report deletions, retained exceptions and validation without changing product behavior.
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.