clean-machinelisted

Audit + clean a developer's machine — dotfolders, caches, language toolchains, package globals — with per-target classification, risk surfacing (auth, processes, side effects), and explicit confirmation. Produces `.forsvn/artifacts/meta/records/machine-cleanup-*.md`. Not for cleaning code (use clean-code) or for triaging user files (those need human review).
hungv47/meta-skills · ★ 9 · AI & Automation · score 75

Install: claude install-skill hungv47/meta-skills

# Machine Cleanup — Orchestrator Audits a developer's machine state and removes abandoned tools, orphaned caches, and unused toolchains — without breaking active workflows. Capability metadata (route triggers, prerequisites, load map, artifact contract) lives in [`routing.yaml`](routing.yaml). Agent table + execution layers + routing rules: [`references/agent-manifest.md`](references/agent-manifest.md). Methodology: [`references/playbook.md`](references/playbook.md). **Core question:** Is this folder still owned by an installed tool I actively use, or is it leftover state from something I no longer have? ## When To Use - New laptop setup; need to start clean. - After trying many AI tools you've now abandoned. - Disk is full or near-full. - Before passing the machine to someone else. - Standalone — no upstream gate required. ## When NOT To Use - Cleaning source code → `/clean-code`. - Triaging files in `Desktop/`, `Documents/`, `Downloads/`, `Pictures/`, `Movies/`, `Music/`, `Public/`, or cloud-mount symlinks — those need human review. - Tool ownership unclear AND you can't identify the owning tool — surface as `NEEDS_CONTEXT` first. ## Critical Gates (The 6 Golden Rules) — load first All 6 fire under `--fast`, Single-Agent Fallback, and dry-run modes: 1. **Never delete user data without explicit confirmation.** Files in `Desktop/`, `Documents/`, `Downloads/`, `Pictures/`, `Movies/`, `Music/`, `Public/`, and any contents under cloud-mount symlinks (`Google Drive`, `On