Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/using-git-worktrees
Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.
Passed 16 of 20 test cases with the skill, and 12 of 20 without it.
and 5 more in the full report
6 fixed12 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to create a git worktree for branch `feature/dark-mode`. The project root has no `.worktrees/` or `worktrees/` folder, and `CLAUDE.md` does not mention any worktree settings. What is the immediate next step?
| Checked | Without skill | With skill |
|---|---|---|
| Prompts the user to choose between project-local .worktrees/ and the global superpowers directory | Missed | Passed |
The instructions your model reads when the skill loads.
Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.
Core principle: Systematic directory selection + safety verification = reliable isolation.
Announce at start: "I'm using the using-git-worktrees skill to set up an isolated workspace."
Follow this priority order:
# Check in priority order
ls -d .worktrees 2>/dev/null # Preferred (hidden)
ls -d worktrees 2>/dev/null # Alternative
If found: Use that directory. If both exist, .worktrees wins.
grep -i "worktree.*director" CLAUDE.md 2>/dev/null
If preference specified: Use it without asking.
If no directory exists and no CLAUDE.md preference:
No worktree directory found. Where should I create worktrees?
1. .worktrees/ (project-local, hidden)
test cases passed, vs 12 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.