Using Git Worktrees
Isolated workspaces: detect existing isolation, prefer native tools, git worktree fallback
- What
- Isolated workspaces: detect existing isolation, prefer native tools, git worktree fallback
- Cost
- Free
- Needs
- an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse) and git worktrees
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — one of the original superpowers meta-skills by @obra (the upstream behind the much-forked framework; distinct from the magentosh/bankai-skills forks already in this catalog and from the obra fiches published at lot 33, using-superpowers and executing-plans). The complete isolation protocol before executing plans: detect existing isolation first (GIT_DIR vs GIT_COMMON, with a submodule guard so a submodule isn't mistaken for a worktree), then prefer the harness's native worktree tools, then fall back to manual git worktrees — never fight the harness. Never pollute the current branch: ask consent before creating a worktree (unless a preference is declared), verify the worktree directory is git-ignored, and announce the isolation at start. Includes the quick-reference table and the rationalizations table ("I'll just be careful on main" is exactly when you need isolation). No other fiche covers workspace isolation. By @obra, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse) and git worktrees Install "Using Git Worktrees" for me. Isolated workspaces: detect existing isolation, prefer native tools, git worktree fallback Repository: https://github.com/obra/superpowers/blob/main/skills/using-git-worktrees/SKILL.md 1. Fetch the SKILL.md file for the obra-using-git-worktrees skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "obra-using-git-worktrees". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.