Notre avis
Nettoie les fichiers temporaires, les tâches obsolètes et réorganise le répertoire ai/ d'un projet.
Points forts
- Automatise le nettoyage des fichiers inutiles et le déplacement des fichiers mal placés.
- Réorganise la documentation dans ai/ en une structure hiérarchique claire.
- Gère les tâches via l'outil 'tk' (marquage, suppression, consolidation).
- Produit un commit Git propre avec un rapport des modifications.
Limites
- Nécessite que l'utilisateur comprenne le but de chaque fichier pour éviter des suppressions incorrectes.
- Dépend de l'outil 'tk' pour la gestion des tâches, qui peut ne pas être présent dans tous les projets.
- La phase d'organisation du répertoire ai/ peut être lente si beaucoup de fichiers sont impliqués.
Quand le projet semble encombré, avec des fichiers éparpillés et des tâches obsolètes, pour restaurer une structure propre.
Si le projet est déjà bien organisé et que vous ne souhaitez pas risquer de perdre des fichiers potentiellement importants.
Analyse de sécurité
PrudenceThe 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.
Exemples
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.
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.