← ClaudeAtlas

clean-cacheslisted

Reclaim disk space by cleaning macOS/Linux dev caches (Docker/OrbStack, package managers, Xcode, Homebrew, kilter, browser caches). Tiered by risk — safe ops run by default, destructive ops require confirmation. Use when the user mentions disk pressure, full disk warnings, "clean up", "free space", or invokes /clean-caches.
usrrname/agent-skills · ★ 0 · Web & Frontend · score 62
Install: claude install-skill usrrname/agent-skills
Reclaim disk space on macOS and Linux. Progressive cleanup grouped by risk tier. ## Process 1. **Triage.** Run `df -h /` and `du -sh ~/Library/Caches ~/.cache /var/cache/apt /var/cache/dnf /Users/Shared/OrbStack ~/Library/Developer 2>/dev/null` to size up. Report top space consumers. 2. **Offer tiers** to user — let them pick scope: - **Safe** — package manager caches + Homebrew (no rebuild cost beyond download) - **Medium** — Docker/OrbStack/Xcode caches (rebuild cost: minutes) - **Project** — kilter cache, project `node_modules`, `.next`/`dist` build artifacts (rebuild cost: seconds-minutes; don't bulk-rm `~/code/`; use project tooling) - **Risky** — macOS Library caches, browser caches (may sign you out / lose state) - **Destructive** — Trash emptying, OrbStack VM reset (confirm each) 3. **For each chosen op**: state what'll be removed, run it, report bytes freed. 4. **Final report**: before/after `df -h /` and total reclaimed. See [[COMMANDS.md]] for the full command matrix per tier. ## Rules - Default to **safe + medium** if user says "clean up" without specifying. - Never run destructive ops without explicit confirmation from the user this session. - Skip categories with <100MB to reclaim (not worth the time). - Don't touch `~/code/` repos directly. Project-level cleanup goes through the project's own tooling (`pnpm`, `kilter destroy`, etc.), not by `rm -rf node_modules` for arbitrary dirs. - Track cumulative bytes freed; report at end. - For `kilter