clean-machine

Audit and clean developer machines with per-target confirmation before deletion.

14|Updated Apr 1, 2026

Search Tags:#audit #toolchains #caches #machine-cleanup #dotfolders #auth-surfaces

Ready to run

npx skills add https://github.com/hungv47/meta-skills --skill clean-machine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-machine
Source: https://github.com/hungv47/meta-skills/tree/main/forsvn-dev/skills/product/clean-machine
Command: npx skills add https://github.com/hungv47/meta-skills --skill clean-machine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Audits and cleans a developer's machine by identifying dotfolders, caches, toolchains, and global installations, surfacing risks and requiring explicit confirmation before any deletion.

Core Features & Use Cases

Per-target classification with risk surfacing (auth, active processes, and side effects).
Generates machine-cleanup records under docs/forsvn/artifacts/meta/records/machine-cleanup-*.md for audit trails.
Safe, user-guided cleanup with explicit confirmation and per-target execution order.

Quick Start

Initiate a cleanup run to scan your home state and confirm each target before removal.

Frequently Asked Questions about clean-machine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely audit and clean dotfolders and caches on a dev machine?▼

To safely audit and clean dotfolders and caches on a dev machine, initiate a scan that classifies targets and surfaces risks like auth tokens or active processes. The tool requires explicit per-target confirmation before any deletion occurs.

What is the best way to identify auth surfaces before removing toolchain files?▼

Identifying auth surfaces before removing toolchain files is handled by scanning your home state for explicit risks. The cleanup process classifies these surfaces and highlights side effects to ensure safe, user-guided removal.

How does machine cleanup handle shell-rc side effects during package globals removal?▼

Machine cleanup handles shell-rc side effects during package globals removal by surfacing them as explicit risks during the audit. You must confirm each target individually before execution to prevent unintended shell configuration breakage.

Can I generate an audit trail for dev machine cleanup records?▼

Yes, you can generate an audit trail for dev machine cleanup records. The process outputs markdown files under docs/forsvn/artifacts/meta/records/ to document the scanned state and integrate with the artifact manifest for future runs.

Does the machine cleanup process require manual confirmation for every deletion?▼

Yes, the machine cleanup process requires manual confirmation for every deletion. It operates with a per-target execution order, ensuring you explicitly approve the removal of each identified dotfolder, cache, or runtime before any action is taken.