using-git-worktrees
Ensures feature work happens in an isolated workspace via git worktrees before executing plans or risky changes.
Anatomy
| Parent repo | obra/superpowers |
|---|---|
| Path | skills/using-git-worktrees |
| Trigger conditions | "Use when starting feature work that needs isolation from current workspace" |
| Instruction format | yaml-frontmatter-md |
| Required tools | git, shell |
| Reusability | universal |
| Complexity | low |
| Ships scripts / examples / tests / boundaries | no / yes / no / yes |
Failure modes
Worktree cleanup after abandoned work is the recurring leak; the skill addresses creation more thoroughly than teardown.
Verdict
Governance disguised as workflow: isolation means a bad agent session costs a worktree, not a working directory. Among the highest safety scores at the skill level.
Related skills
Blocks the agent from claiming work is complete, fixed, or passing until it has run verification commands and confirmed output. Evidence…
Forces root-cause investigation before any fix: reproduce, hypothesize one cause at a time, test the hypothesis, then patch. Bans…
Frequently asked questions
What does the using-git-worktrees skill do?
Ensures feature work happens in an isolated workspace via git worktrees before executing plans or risky changes.
When does using-git-worktrees trigger?
Its stated trigger: "Use when starting feature work that needs isolation from current workspace". Trigger precision is a scored reliability dimension.