← ClaudeAtlas

forge-uninstalllisted

Remove Forge filesystem state from the current project, and optionally global state, with a mandatory preview step before any deletion. Use this skill whenever a user types `/forge:uninstall`, says "remove Forge", "I want to uninstall this plugin", "clean up Forge files", "delete pipeline/", expresses frustration suggesting they may give up on Forge, or asks to start over from scratch. Make sure to ALWAYS run with `--dry-run` first and present the plan to the user; NEVER proceed to actual removal without an explicit user confirmation in the same turn. This skill does NOT unregister the plugin from Claude Code itself — always remind the user to run `/plugin uninstall forge@forge-plugins` as a separate step after filesystem removal.
tonmoy007/forge-plugins · ★ 1 · Data & Documents · score 72
Install: claude install-skill tonmoy007/forge-plugins
# Forge Uninstall Removes Forge filesystem state — `pipeline/` artifacts, `.forge/` runtime state, and optionally `~/.forge/` global lessons — from the user's project. Does **not** remove the Claude Code plugin registration; that's a separate `/plugin uninstall` action. ## When to Use - User types `/forge:uninstall` or `/forge:remove` - User says "uninstall Forge", "remove Forge from this project", "I want to start over" - User says "clean up Forge files", "remove .forge/", "delete pipeline/" - User is frustrated and considering abandoning Forge — offer this as a clean exit - User wants to migrate a project away from Forge while keeping the SDLC documents - User asks "how do I undo `/forge:init`?" ## Steps 1. **Always preview first.** Run a dry-run BEFORE any destructive action: ```bash python ${CLAUDE_PLUGIN_ROOT}/scripts/uninstall.py --dry-run --cwd "<project>" ``` 2. Present the full plan output **verbatim** to the user. Do not paraphrase what will be removed; the user needs to see the exact paths, file counts, and sizes 3. Ask for an explicit confirmation: "Should I proceed with removal? Reply 'yes' to confirm, or tell me to keep artifacts / include global state if those apply." 4. Only after the user replies with an unambiguous yes (or equivalent — "do it", "go ahead", "remove it"), run the actual removal: ```bash python ${CLAUDE_PLUGIN_ROOT}/scripts/uninstall.py --cwd "<project>" --yes ``` 5. If the user said "keep my SRS / specs / pipeli