About this skill

Problem

A Windows C drive often runs out of space because temporary files, browser caches, package-manager caches, and large AppData folders accumulate over time. Manual cleanup is easy to over-scope: hidden paths are missed, running components are touched, and report output can disappear if temporary directories are cleared too early. This skill constrains cleanup into an auditable, staged, and user-confirmed ops workflow.

How It Works

It progresses through Phase 1: baseline cleanup, Phase 2: deep analysis, and Phase 3: junction migration:
- Baseline cleanup: records C and D drive free space, then clears low-risk items such as %TEMP%, C:\Windows\Temp, Chrome/Edge caches, thumbnail caches, pip cache purge, and the Recycle Bin, while skipping locked paths like qoder-cli.
- Deep analysis: uses scan_disk.ps1 to rank top-level C drive folders, AppData\Local and AppData\Roaming entries, dotfolders, installed programs, and caches from WeChat, WPS, Bilibili, Douyin, Steam, and updaters. It separates safely cleanable caches, app-managed caches, candidate uninstallations, and system-required items.
- Junction migration: after confirming that target apps are closed, runs migrate_junctions.ps1 to map large AppData directories to a secondary drive, moves package-manager caches and environment variables, then verifies links and settings with verify_junctions.ps1.

Boundaries

It is aimed at personal Windows workstations needing emergency C drive relief, not disk quota governance, centralized log auditing, or fleet-wide IT automation. Target applications must be closed before migration; Microsoft, Packages, Programs, and the running QoderWork process should not be moved. Locked files may require a post-reboot retry. Check secondary-drive capacity, permissions, and backup strategy before running destructive steps.

Screenshots

Use Cases

When the C drive drops below 10GB and temp files, browser caches, and Recycle Bin are large, run baseline cleanup.
After cleanup, scan AppData, installed programs, and WeChat, WPS, or Bilibili caches to list safe cleanup candidates with sizes.
Migrate large AppData Local directories to the D drive with junctions after closing the target applications so original paths keep working.
Move package-manager caches off the C drive, update environment variables, and verify the new paths afterward after restart if files were locked.

Best For

Windows workstation admins: C drive full but unsure which caches are safe, needing staged cleanup reports.
AI tool users: local models, CLIs, or QoderWork caches filling C drive, needing path migration checks.
Software engineers: pip or package-manager caches on C drive, needing cache relocation and env updates.
Ops on-call staff: resolving C drive space alerts with reviewable PowerShell workflows.