← ClaudeAtlas

windows-disk-cleanuplisted

Free space on a full Windows drive without losing user data - find what is consuming the system drive, delete only regenerable caches, and relocate the rest to another drive via NTFS junctions or environment variables. Use whenever the user mentions a full or nearly full C drive, low disk space on Windows, a huge AppData folder, "C盘满了", "C盘爆红", "C盘清理", "磁盘空间不足"; wants to move any cache, AppData folder, package cache, or app data directory to another drive (NuGet, npm, pip, Playwright, Cargo, Unreal Engine DDC, Feishu/Lark, Slack, Discord, NVIDIA shader cache, Claude transcripts); asks whether a cache or app folder is safe to delete, or whether deleting it will log them out, lose chat history, or break the app; or asks what is taking up space on their system drive - even if they never say "cleanup". Also use when a Windows disk is near full and apps behave strangely, since a full volume silently corrupts SQLite databases.
linad3d/drivekeeper · ★ 1 · AI & Automation · score 77
Install: claude install-skill linad3d/drivekeeper
# Windows Disk Cleanup & Relocation Recover space on a full Windows system drive **without losing a single piece of user data**, and make the space stay recovered. ## Deleting is the easy half; the space comes back A cleanup that only deletes is undone in about two weeks. Measured on one workstation 13 days after a run: - Deleted-only locations regrew **11.25 GB** on C: (`%LOCALAPPDATA%\Temp` 10.94 GB, NVIDIA `DXCache` 0.31 GB) - roughly **0.87 GB/day**. - Relocated applications produced **5.32 GB** of new data over the same period, and **none of it landed on C:** - including 5.76 GB of new chat-client cache. That difference is the point of this skill. A junction is a filesystem-level redirect resolved below the application layer, so the app keeps opening the path it always used and never learns its data moved - which means its *future* growth follows the link automatically. **So wherever something is too valuable to delete or certain to regrow, relocate it rather than just clearing it.** Deleting alone means doing this again next month. The second reason to act, and to act early: a Windows volume that runs to zero bytes does not fail loudly. It silently corrupts whatever was mid-write. In the incident this skill was built from, a full C: drive truncated Chrome's `History` SQLite database into an empty shell, and Chrome kept running without recording anything until it was restarted - the loss was discovered days later, and the pre-incident history was unrecoverable