charles-storage-cleanup
Storage Cleanup
Recover space from confirmed disposable artifacts, explain recent growth, and preserve active work. Measure success with free bytes on the actual data volume.
Scope and authorization
When the request authorizes removing unused files, delete confirmed disposable candidates without repeated confirmation. An inventory-only request stays read-only. Skill discovery alone grants no deletion permission. Carry forward the user's selected items, exclusions, age limits, and recent-use conditions across passes; a request to inspect more locations does not revoke a previous keep instruction.
Keep active apps, builds, Git writers, and emulators running. Do not cancel a job to turn its files into deletion candidates. Preserve source, uncommitted work, credentials, unique research/media, current releases, and persistent VM/container data unless their removal is explicitly authorized. A generic request to clear unused files does not supply that authorization. An old modification time, ignored Git status, or absent open handle alone does not establish disposability. Skip uncertain candidates and continue useful cleanup elsewhere.
Choose the depth
- For a named deletion, inspect that selection and its dependencies, then complete the authorized cleanup. A whole-app uninstall includes its own helpers and startup registrations; cache-only cleanup does not.
- For general cleanup, unused-app reviews, "what else," or "search more extensively," use the discovery checklist. Cover installed software, both Library trees, hidden package stores, runtimes, developer/research output, devices, media/downloads, and OS-managed storage. Do not stop at the largest project or
~/Library/Caches. - When explaining a large folder, break it into source, generated output, installed environments, Git history, and unique assets. Describe what the largest payloads actually contain and why they exist before recommending removal.