cleanup-unused-files

To safely delete large build and cache files, you can explicitly define the blast radius before removing directories like target/, dist/, and .next/. This targets specific output paths to reclaim disk space without unintended data loss.

Clearing package manager and SDK caches such as ~/.npm, ~/.bun, and ~/.rustup removes stored dependency data. This resets the machine's developer state to free up storage without requiring you to immediately re-download everything.

Yes, you can use a script to reset developer state and clean up build directories across your machine. This approach requires permission to modify system directories and delete files to successfully clear large caches.

Blast radius control works by letting you explicitly define which directories are targeted for file deletion before any data is removed. This ensures that only specified cache and build directories are affected during the cleanup process.

Yes, you need permission to modify system directories and delete files when performing cleanup tasks. This access is required to successfully remove large cache and build files from protected paths.