using-git-worktrees

Topics in the source

• Using Git Worktrees
• Overview
• Directory Selection Process
• 1. Check Existing Directories
• 2. Check CLAUDE.md
• 3. Ask User
• Safety Verification
• For Project-Local Directories (.worktrees or worktrees)

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: If found: Use that directory. If both exist, .worktrees wins. If preference specified: Use it without asking. If no directory exists and no CLAUDE.md preference: MUST verify directory is ignored before creating worktree: If NOT ignored: Per Jesse's rule "Fix broken things immediately": 1. Add appropriate line to .gitignore 2. Commit the change 3. Proceed with worktree creation Why critical: Prevents accidentally committing worktree contents to repository. No .gitignore verification needed - outside project entirely. Auto-detect and run appropriate setup: Run tests to ensure worktree starts clean: If tests fail: Report failures, ask whether to proceed or investigate. If tests pass: Report ready. | Situation | Action | |-----------|--------| | .worktrees/ exists | Use it (verify ignored) | | worktrees/ exists | Use it (verify ignored) | |

This is an excerpt. Refer to the complete source and its current requirements.