Using Git Worktrees Skill

When to Use

• Working on multiple features simultaneously
• Need to context-switch without stashing
• Running long tests on one branch while working on another
• Reviewing PRs while working on a feature

When NOT to Use

• Single-branch work with no concurrent development — worktrees add overhead with no benefit
• When a quick stash is sufficient — if you need to context-switch for less than 5 minutes, git stash is lower friction
• When disk space or Node.js/dependency install times are a concern — each worktree needs its own node_modules
• On shared machines or CI environments where worktree paths are not predictable

What Are Git Worktrees?

Git worktrees allow you to have multiple working directories from the same repository, each checked out to a different branch.