using-git-worktrees

Git worktrees create isolated workspaces for each branch, letting you develop multiple features simultaneously without context switching. Each worktree has its own directory and checked-out branch, keeping changes separate and preventing accidental interference between features.

Use git worktrees to isolate each feature in a dedicated workspace. This eliminates merge conflicts from concurrent edits in the same directory and keeps your primary workspace clean while you develop on separate branches.

Git worktrees automatically detect your project type—npm, Cargo, Python, Go—and run setup commands like npm install or cargo build. The skill verifies .gitignore configuration and validates a clean baseline with tests before you start development.

Yes. Worktrees create completely isolated directories for each branch, leaving your main workspace untouched. You can continue working on one feature while exploring or testing others in separate worktrees.

No. The skill automatically detects project tooling and handles setup for npm, Cargo, pip, poetry, and Go. It also verifies .gitignore entries to ensure worktree contents won't be accidentally committed.

Use worktrees when you need to maintain multiple branches checked out simultaneously without rebuilding dependencies or disrupting tests. Branch switching requires stashing changes and rebuilding; worktrees keep everything ready and isolated.