Disk Garbage Cleanup Master

Problem

Windows user directories accumulate old installers, test caches, large logs, and empty folders. Manual deletion is risky because project directories, WPS data, or system files can be removed by accident. This skill targets IT operations by turning risky cleanup into a reviewable, confirmable workflow. It materializes the deletion list in a document, which is useful on shared machines, development machines, or operations machines.

Workflow

It runs in three stages: scan, generate review file, clean after confirmation. The scan step asks for a target path and parameters such as --old-days 180, --large-mb 100, --quick, and --exclude, then emits JSON results. The generation step writes Trash.md to the desktop, grouped by cache directories, temporary files, old files, large files, and empty folders. Files from the same project are merged into one row, while complete Windows absolute paths are retained. Before cleanup, the skill warns the user again and then runs deletion, moving items to the Recycle Bin by default. --no-recycle is used only when explicitly requested. System files such as desktop.ini and ntuser.dat.LOG* are routed to the excluded section instead of the cleanup list.

Boundaries

Use it for user profiles, project caches, and test environment leftovers. It does not guess file purpose; it reports objective facts such as size, age, and type, and stops when deletion fails so the user can decide. Batch processing limits item count per batch to reduce the scope of a single operation. Avoid using it as a full-disk deep cleaner, especially on C:\Windows or Program Files. Files whose purpose is unclear should remain in Trash.md for manual review.