← ClaudeAtlas

tidyinglisted

Finds junk files (backups, temp, stray notes) and removes them reversibly after your ok. Use when the user asks to clean up the project, remove leftovers, or says the repo is messy. Not for refactoring code.
t8jwscc7qy-sketch/foma-skills · ★ 2 · AI & Automation · score 78
Install: claude install-skill t8jwscc7qy-sketch/foma-skills
Finds unneeded files, shows a manifest, and removes only what the user approves, in a way that can be undone. Report first, nothing changes before the ok. ## Steps 1. Read the CLAUDE.md contract (`## Where things live`: Docs, Plans, Scratch, Trash). Not a git repo: say so and stop (nothing is recoverable). `$ARGUMENTS` only narrows the path. 2. Detect without reading file contents: `git status --short -uall`, `git ls-files --others --exclude-standard`, `git ls-files --others --ignored --exclude-standard --directory`, `find` for zero-byte files and empty dirs (skip `.git`, `node_modules`, venvs, build output). 3. Sort every candidate into a tier. **T1** safe to remove: OS junk, backup and merge leftovers, Claude temp, zero-byte strays, empty dirs. **T2** needs a look: untracked scratch or debug scripts, `.md` outside the docs home, logs, screenshots, large untracked files, finished plans (archived, never deleted). **T3** never touched: `.env*`, keys, data, assets, untracked source that matches no T1 pattern, `.git`, nested repos. 4. A T2 item is only listed when it has a second signal: no `grep -r` reference to its name and not modified for 30 days (`find <path> -mtime +30`). A detector (knip, vulture, cargo-machete) counts as one signal only if the project already has it; never install one. 5. Show the manifest, grouped by tier and by kind: path, size, tracked or untracked, why. Show T3 as a count only. Compact: more than 30 items per group → counts plus the first 10 and the