Claude Pc Cleanup

pc-cleanup

A [Claude Code](https://claude.com/claude-code) skill that scans a macOS machine for reclaimable disk space and cleans it up safely — the kind of "disk almost full" problem every developer's Mac eventually runs into, mostly from package manager caches, old build artifacts, and `node_modules` piling up across projects.

Instead of guessing what's safe to delete, it:

1. Scans — a read-only pass over the usual suspects: ~/Library/Caches, ~/.cache, dev toolchain caches (npm/pnpm/uv/bun/cargo/go/cocoapods/ homebrew/playwright), old Claude Code CLI versions, Xcode DerivedData, container/VM runtimes (Podman/Docker), iOS Simulator devices, the Trash, Homebrew's own cleanup candidates, Downloads, and — per project — every node_modules / venv / .terraform/providers it can find.
2. Classifies everything into three tiers: safe & fully regenerable, regenerable-but-needs-your-judgment (a running Podman VM, Downloads contents, etc.), and never-touch (.git, terraform.tfstate, /System, your home directory).
3. Shows you the plan — sizes, tiers, and why each item is safe (lockfile present, OS cache convention, already in Trash, etc.) — before touching anything.
4. Only deletes what you approve, through a guardrailed script that re-derives the safety rules in code, so a misread instruction can't accidentally delete something it shouldn't.

It's built to be run repeatedly — it logs what it frees over time to `~/.claude/pc-cleanup-history.log` — rather than a one-off script.

Why not just a shell script?

A fixed script can't tell a `node_modules` backed by a lockfile (trivially safe to delete) from one that isn't, can't tell you *why* `~/Library/Caches` is safe to clear, and can't have a conversation with you about the judgment calls (a running Podman VM, a `venv` with no `requirements.txt`, files in Downloads). That reasoning is the actual value here — the bundled scripts just do the deterministic