Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ibrahim-3d/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 15 of 20 test cases with the skill, and 12 of 20 without it.
and 1 more in the full report
4 fixed13 passed either way5 still failing0 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.
Development and pull request review on `feature/auth` in `.worktrees/auth` is finished and merged. Which companion workflow is designated for cleaning up this worktree?
| Checked | Without skill | With skill |
|---|---|---|
| Refers to finishing-a-development-branch skill for post-merge worktree cleanup | 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_search -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.