Git Worktrees

Manage the full worktree lifecycle: create → work → resolve → clean up.

Core Philosophy

1. Worktrees are temporary. Create for a task, remove when done. Lingering worktrees waste disk and create confusion.
2. One branch, one worktree. Git enforces this — a branch can only be checked out in one worktree at a time.
3. Always clean up. After merging or closing a PR, ask the user to remove the worktree and delete the branch. Never leave stale worktrees behind.
4. Fetch before creating. Run git fetch origin before git worktree add to ensure you have current remote state.
5. Dependencies are per-worktree. Each worktree needs its own npm install, pip install, etc. — build artifacts are not shared.

Lifecycle