cleanup-audit
Skill1 starsChanged 6 months agoMITView on GitHub
Use after substantial edits, refactors, moves, generated changes, or long agent sessions to find leftovers, stale stubs, unused imports, accidental compatibility artifacts, and trash files. Remove only confirmed non-behavioral leftovers; report anything that may affect compatibility or runtime behavior before changing it.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- sohei56/maul-teamtheir own version, first seen Aug 8, 2026
- kickbaron0-star/skillstheir own version, first seen Apr 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- sohei56/maul-team★ 17same name
- kickbaron0-star/skills★ 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 repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-self-checkSkill
- biome-grit-rulesSkill
- biome-toolingSkill
- bun-testSkill
- bun-workspaceSkill
- code-reviewSkill
- dispatch-satelliteSkill
- docs-managementSkill
- docs-readingSkill
- effect-concurrency-lifecycleSkill
- effect-errors-schemaSkill
- effect-observability-timeSkill
- effect-services-layersSkill
- effect-testing-runtimeSkill
- effect-v4Skill
- jsx-md-authoringSkill
- monorepo-maintenanceSkill
- refactoring-disciplineSkill
- roadmap-managementSkill
- runtime-engineSkill
- server-runtimeSkill
- testing-patternsSkill
- theseus-designSkill
- tool-authoringSkill
- typescript-strictSkill
- ui-layout-disciplineSkill
- theseus-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
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 8
Use this skill as a finishing pass after substantial work.
- Distinctive: line 12
Leave the repo without obvious agent leftovers:
- Distinctive: line 25
Delete only when the artifact is proven unused, non-public, and non-behavioral.
- Distinctive: line 27
If removal might change imports, package exports, runtime behavior, persisted data handling, public contracts, or downstream compatibility, …
- Distinctive: line 31
Do not use this skill to redesign code or remove live compatibility paths without confirmation.
- Distinctive: line 37
When cleanup collides with compatibility, preserve behavior and report the stale path.
- Very specific: line 42
Search old names, moved paths, and temporary terms with rg.
- Distinctive: line 43
Check for empty files, stub files, and single-line re-export wrappers.
- Distinctive: line 44
Check barrels and package exports for accidental old/new duplication.
- Distinctive: line 45
Check imports for old paths, broad namespace artifacts, and unused leftovers.
- Distinctive: line 46
Check tests, docs, and comments for stale names introduced by the change.
- Distinctive: line 47
Remove only confirmed non-behavioral leftovers.
- Distinctive: line 59
test fixture files with no imports and no package export path
- Distinctive: line 64
Do not delete without confirmation:
- Distinctive: line 80
Use searches shaped by the actual change:
- Distinctive: line 96
If nothing was removed, say so clearly and list any concerns found.
≈ “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
Cleanup Audit
Use this skill as a finishing pass after substantial work. This is a cleanup and review pass, not a refactor pass.
Goal
Leave the repo without obvious agent leftovers:
- empty stubs
- unused imports
- stale comments
- accidental re-export wrappers
- old names in nearby docs or tests
- duplicate files created during moves
- scratch artifacts
- broad import artifacts introduced to avoid updating call sites
Core Rule
Delete only when the artifact is proven unused, non-public, and non-behavioral.
If removal might change imports, package exports, runtime behavior, persisted data handling, public contracts, or downstream compatibility, stop and report it as a concern instead of deleting it.
Not A Refactor
Do not use this skill to redesign code or remove live compatibility paths without confirmation.
- Cleanup removes confirmed trash.
- Refactoring changes structure or behavior.
- Compatibility removal is a breaking change unless the user explicitly authorized it.
When cleanup collides with compatibility, preserve behavior and report the stale path.
Workflow
- Inspect
git diff --statand changed files to understand the work surface. - Search old names, moved paths, and temporary terms with
rg. - Check for empty files, stub files, and single-line re-export wrappers.
- Check barrels and package exports for accidental old/new duplication.
- Check imports for old paths, broad namespace artifacts, and unused leftovers.
- Check tests, docs, and comments for stale names introduced by the change.
- Remove only confirmed non-behavioral leftovers.
- Report concerns separately from removed cleanup.
Safe Cleanup Targets
Usually safe when verified unused:
- empty files that are not imported or exported
- unused imports
- scratch files produced by local experiments
- comments created by the current change that describe obsolete temporary state
- duplicate local helpers with no callers
- test fixture files with no imports and no package export path
- docs or comments that mention an old name where the new name is unambiguous
Red Flags
Do not delete without confirmation:
- exported symbols
- package
exports - public barrels
- compatibility aliases or shims
- migration or fallback code
- persisted-data readers
- server, RPC, protocol, or serialized contract fields
- docs archive or design history
- files still imported anywhere
- behavior branches with active tests
- wrappers that may be used by downstream consumers
Search Prompts
Use searches shaped by the actual change:
- old file stem, new file stem
- old exported names, new exported names
legacy,compat,deprecated,alias,old,v1,temporary,for now,TODO- removed path fragments
- package export paths and barrel names
Report Format
In the final report:
Removed: confirmed non-behavioral leftovers.Concerns: possible stale paths that need confirmation before removal.Verification: searches and checks run.
If nothing was removed, say so clearly and list any concerns found.
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.

