← ClaudeAtlas

detachlisted

Detach this repo from rhiza — delete every rhiza-managed file listed in .rhiza/template.lock, prune the emptied directories, and remove the lock file. DESTRUCTIVE; prompts for confirmation unless --force is passed.
Jebel-Quant/rhiza-claude · ★ 4 · Data & Documents · score 70
Install: claude install-skill Jebel-Quant/rhiza-claude
You are running `/detach` in the **current working directory's repo**. **This command is a thin wrapper around the bundled `plugin/scripts/detach.py`.** All the deletion logic lives in that script — a deterministic, stdlib-only Python program that reads `.rhiza/template.lock` directly (no `rhiza` CLI, no PyYAML required). Do **not** re-implement it or delete files yourself; run the script. ⚠️ **This is destructive.** It permanently deletes the files rhiza synced into the repo, removes the directories they leave empty, and deletes `.rhiza/template.lock` so the repo is no longer rhiza-managed. Files you added yourself are untouched. **This detaches a repo, not the plugin.** It is the inverse of the *sync*, not of the installation — the rhiza plugin stays installed and every other repo stays managed. A user who wants the plugin itself gone from Claude Code wants `/plugin`, not this. If that is what they appear to be asking for, say so rather than deleting their files. Argument (optional): `$ARGUMENTS` — a path to the repo root to clean; default is the current directory. ## 1. Confirm intent first Because this deletes files, **confirm with the user before running** unless they have already clearly asked to proceed (e.g. said "yes, detach" or passed `--force`). Recommend they have a clean git tree / committed work first, so the deletion is easy to review and revert. ## 2. Run the script Invoke it with the plugin-root path (it ships inside this plugin, so `${CLAUDE_PLUGIN_ROO