using-git-worktrees

Git worktrees create isolated workspaces for different branches in a single repository. Each worktree has its own directory, allowing you to develop features, fixes, or experiments in parallel without stashing or switching branches, eliminating context-switching overhead.

The skill validates worktree locations, checks `.gitignore` to prevent accidental tracking of worktree contents, and adds worktree paths automatically if needed. It detects your project type and installs dependencies before running baseline tests.

Yes. Git worktrees work with any project type. The skill auto-detects your environment—npm, cargo, pip, poetry, or go mod—and runs the appropriate dependency installation and tests after creating the worktree.

Use worktrees when you need parallel work on multiple branches without duplicating the entire repository. Worktrees save disk space, share Git history, and streamline workflows like fixing a critical bug while keeping a feature branch under review intact.

The skill reports test failures and requires explicit user confirmation before proceeding. This prevents broken worktrees from entering your workflow and ensures each workspace starts in a valid state.