Create and manage git worktrees for parallel coding sessions with zero dead time. Use when blocked on tests, builds, wanting to work on multiple branches, context switching, or exploring multiple approaches simultaneously.
88
81%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Worktree creation workflow and naming
Lists worktrees first
100%
100%
Sibling path for feature
100%
100%
Sibling path for hotfix
100%
100%
Sibling path for experiment
100%
100%
New branch flag for experiment
100%
100%
Feature branch checkout
100%
100%
Hotfix branch checkout
100%
100%
New-session instructions
100%
100%
Three worktrees created
100%
100%
Correct add syntax
100%
100%
Safe worktree cleanup and guardrails
git -C status for feat
100%
100%
git -C status for fix
100%
100%
git -C status for exp
100%
100%
Status before remove ordering
100%
100%
Worktree remove commands
100%
100%
git worktree prune
100%
100%
Same-file warning
100%
100%
Uncommitted changes warning
100%
100%
Correct remove syntax
100%
100%
Prune after removes
100%
100%
Claude Code worktree integration
claude -w or --worktree flag
100%
100%
Flag used for multiple sessions
100%
100%
Auto-cleanup noted
0%
100%
isolation: worktree in CLAUDE.md
100%
100%
Two subagent entries
100%
100%
Isolation on both subagents
100%
100%
Ctrl+F kill-agents shortcut
0%
100%
Two-press confirmation noted
0%
100%
Ctrl+B background shortcut
0%
100%
Isolation explanation
100%
100%
1de1554
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.