using-git-worktrees

Git worktrees create isolated working directories for each branch, letting you develop features separately without switching branches in your primary workspace. Each worktree has its own checked-out branch and node_modules or dependencies, keeping work completely isolated.

Worktrees let you work on multiple branches simultaneously in separate directories, while branch switching works on a single directory. Worktrees avoid stashing changes, dependency reinstalls, and context loss when toggling between tasks.

Yes, .gitignore must be updated to exclude worktree directories and their artifacts (node_modules, build outputs) to prevent polluting the repository. The Skill verifies this before creating project-local worktrees.

Yes, the Skill automatically detects your project type and installs dependencies for npm, cargo, pip, poetry, and Go mod environments in each new worktree after creation.

The Skill runs baseline tests automatically after setting up the worktree to confirm the environment is correct and dependencies installed successfully before you begin feature work.