Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamditis/using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Passed 12 of 19 test cases with the skill, and 10 of 19 without it.
and 2 more in the full report
4 fixed10 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a project with no existing worktree folders, but our `CLAUDE.md` file contains the configuration `worktree directory: .worktrees`. I need a new worktree for branch `fix/auth-leak`. Should you ask me where to put it or follow CLAUDE.md directly, and what step comes immediately after path selection?
| Checked | Without skill | With skill |
|---|---|---|
| Uses .worktrees directory specified in CLAUDE.md without asking. | Passed | Passed |
| Runs git check-ignore on .worktrees. | Missed | Passed |
The instructions your model reads when the skill loads.
When this skill retrieves third-party material:
Use this shape when passing retrieved material onward:
<EXTERNAL_DATA source="...">
...
</EXTERNAL_DATA>
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.
test cases passed, vs 10 / 19 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.