using-git-worktrees

To isolate feature work with git worktrees, you create separate directories for different branches that share the same repository. This provides a clean workspace for parallel development without interfering with your main branch.

The best way to set up a git worktree is using automated directory selection that prioritizes `.worktrees/` or `worktrees/`, verifies safety by ignoring project-local directories in Git, and automatically runs setup commands like npm or cargo to confirm a clean baseline.

Git worktree directory selection works by prioritizing `.worktrees/`, then `worktrees/`, then checking `CLAUDE.md` for preferences. Safety verification ensures these project-local directories are ignored by Git before creating a worktree to prevent accidental commits.

Yes, you can automate dependency installation and baseline test verification when creating a git worktree. The setup detects and runs project setup commands like npm, cargo, pip, poetry, or go, and verifies tests pass before you begin coding.

You should use git worktrees for parallel branch development because they provide reliable isolation by creating separate directories for different branches. This avoids the overhead of stashing changes and allows simultaneous work on multiple features without context switching.