Our review
Cleans up temp files, stale tasks, and reorganizes the ai/ directory of a project.
Strengths
- Automates removal of unnecessary files and relocation of misplaced files.
- Reorganizes ai/ documentation into a clear hierarchical structure.
- Manages tasks via the 'tk' tool (marking done, deleting stale, consolidating duplicates).
- Produces a clean Git commit with a summary of changes.
Limitations
- Requires the user to understand each file's purpose to avoid incorrect deletions.
- Depends on the 'tk' tool for task management, which may not be present in all projects.
- The reorganization phase of the ai/ directory can be slow if many files are involved.
When the project feels cluttered with scattered files and stale tasks, to restore a clean structure.
If the project is already well-organized and you don't want to risk losing potentially important files.
Security analysis
CautionThe skill leverages Bash for file cleanup operations. While not inherently malicious, it has the potential to delete important files if the user misjudges their purpose. No network or obfuscation concerns.
- •Uses Bash to delete and move files, which could lead to accidental data loss if misapplied.
Examples
Run the prune skill to clean up temp files, stale tasks, and organize the ai/ directory.Use prune to remove unnecessary files from the root directory and move misplaced ones to appropriate folders.Apply the prune skill to reorganize the ai/ folder: consolidate duplicate topics and split overly broad files.name: prune description: Clean up temp files, stale tasks, and organize ai/ directory. allowed-tools: Read, Write, Edit, Glob, Grep, Bash
Prune
Clean up project cruft. Run when things feel cluttered.
1. Survey
ls -la
ls -la ai/ ai/**/* 2>/dev/null
tk ls
git status --short
2. Clean
Files: For each file in root and other unexpected places—does it serve an ongoing purpose?
- No purpose → delete it
- Has purpose, wrong location → move to proper place (tests/, scripts/, etc.)
- Has purpose, right location → keep
Examples:
test.pyin root, throwaway → deletetest.pyin root, useful test → move to tests/debug.shworth keeping → move to scripts/benchmark.pywith structure → keep (ongoing tooling)
The difference is purpose, not name. Ask when uncertain.
Don't touch: .git/, config files, source code
Tasks: Mark completed done, delete stale ones, consolidate duplicates.
3. Organize ai/
Goal: hierarchical organization where agents can find any topic easily.
- Overview docs at top level for high-level context
- Detailed docs split out by specific topic
- One doc per topic - no scattered duplicates
Read each file to understand its content before acting.
Root files:
- STATUS.md - prune aggressively (resolved blockers, completed work, outdated state)
- DESIGN.md - update if stale (remove descriptions of deleted code)
- DECISIONS.md - keep all entries (it's a log)
- SPRINTS.md - update sprint status
Subdirs (research/, design/, sprints/, etc.):
- Consolidate scattered content on same topic into one file
- Split multi-topic files into focused single-topic docs
- Leave alone if already well-organized
Preserve all important content. Delete old files only after content is safely moved. If already well-organized, say so and move on.
4. Finish
git add -A
git diff --cached --stat # review what changed
git commit -m "Prune: clean up and organize"
Report what was removed, reorganized, or left alone.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.