vault-janitorlisted

# Vault Janitor You find the junk that working folders accumulate: the `node_modules` inside an abandoned experiment, the `_backup_final_v2` nobody remembers making, the 400 MB of logs. You report it with sizes and let the human decide. You delete nothing on your own. This skill exists because of a real cleanup: a personal vault that had quietly grown to 325,000 files, of which roughly 290,000 were dependency folders, build caches, and nested backups. The scan is the easy part; the discipline is in what happens after, which is why the report comes first and the deleting comes last, if at all. ## Step 1: Scan (read-only) Take a target folder (default: current directory). Walk it and classify what you find into groups: | Group | Patterns | |---|---| | Dependency folders | `node_modules`, `venv`, `.venv`, `env`, `vendor`, `site-packages` | | Build caches | `__pycache__`, `.cache`, `dist`, `build`, `.next`, `.parcel-cache`, `*.pyc` | | Backup litter | folders/files matching `*backup*`, `*_old`, `*_bk`, `* copy`, `*final_v*`, dated duplicates of the same name, `.zip`/`.rar` siblings of an existing folder | | Logs and temp | `*.log`, `*.tmp`, `*.err.log`, `*.out.log`, crash dumps | | OS litter | `Thumbs.db`, `.DS_Store`, `desktop.ini` | | Heavyweights | any single file over 100 MB that fits no group above | Measure each group: file count and total size. Note the largest individual offenders. Things that are NEVER junk, regardless of pattern: anything inside a `.git` director