git-worktrees

Git worktrees create isolated branch environments so multiple Claude Code instances work simultaneously without conflicts. Each worktree maintains separate file state and branch context, letting you switch between tasks instantly without stashing or committing.

Git worktrees let you maintain a dedicated worktree for long-running refactors on a separate branch while your main worktree stays unblocked. Background work continues in isolation, and you merge when ready without interrupting primary development.

Run scripts/create_worktree.sh, which prompts for a feature name, validates your repository, creates a new branch, configures the worktree location, and opens a Claude Code session. Use /init in the new session to orient Claude with worktree context.

Yes. Create a worktree from your base branch for the hotfix, work in isolation without affecting main development, then merge back. This workflow prevents hotfixes from tangling with in-progress features on your primary branch.

The Skill provides scripts and workflows to create, list, cleanup, and sync Git worktrees. After work completes, cleanup removes the worktree and branch; sync operations keep changes coordinated across parallel sessions.

The Skill handles Git operations through automation scripts, but basic familiarity with branches and merging helps. The /init command orients Claude within your worktree so context transfer is seamless.