houseclean

Cross-drive storage auditing surveys all connected drives to map free space and identify space hogs like orphaned git worktrees, AI tool caches, and build artifacts. It then generates a prioritized action plan with exact migration commands to safely reclaim disk space.

The best way to move npm and pip caches is to generate a concrete migration plan with precise commands tailored to your drive configuration. This ensures caches and project artifacts are relocated correctly to the target drive without breaking existing dependencies.

Safely cleaning up orphaned git worktrees requires an audit to identify merged branches and stale directories. The cleanup process includes safety guardrails that never delete data without explicit user confirmation, ensuring only safe worktrees and empty directories are removed.

Yes, cross-drive cleanup applies to Windows and common project environments. It specifically scans for AI tool caches like .ollama, .gemini, and .cursor, identifying these large reusable data sources so you can migrate them and reclaim disk space.

No, disk space migration will never delete data without user confirmation. The process enforces safety guardrails that document every step for auditing, migration, and verification, ensuring you have full control over what is cleaned or moved.

Your drive runs out of space because build artifacts like node_modules and .venv directories accumulate quickly across projects. A storage audit surfaces these large project artifacts and provides exact commands to migrate or clean them up efficiently.