using-git-worktrees

Git worktrees create isolated directories for different branches within the same repository, letting you work on multiple features concurrently. Each worktree is a separate checkout sharing the same .git directory, so you avoid branch switching and merge conflicts.

Yes. The Skill supports project-local worktrees in a .worktrees directory and checks .gitignore to ensure safety before creating them. It also respects CLAUDE.md preferences for custom locations if specified.

The Skill auto-detects your project tooling (npm, Cargo, pip, pyproject.toml, go.mod) and runs install, build, and test commands automatically, delivering a ready-to-code environment in the new worktree.

Each worktree is an independent checkout of a different branch, so changes in one worktree don't affect others until explicitly merged. You work in isolation, reducing accidental conflicts when multiple features are in flight.

Worktrees are persistent directories under .worktrees or a custom location. You can delete them manually or integrate cleanup into your workflow after merging; the Skill creates them but doesn't auto-remove them.

The Skill detects package.json, Cargo.toml, requirements.txt, pyproject.toml, and go.mod. If your project uses a different build system, you'll need to run install and test commands manually in the worktree after creation.