using-git-worktrees

Git worktrees create isolated workspaces for parallel feature development. Each worktree is a linked checkout of your repository at a different branch, letting you work on multiple features simultaneously without switching branches or stashing changes in your main workspace.

Create a worktree by running a command that generates an isolated workspace, verifies your `.gitignore` includes the worktree directory, and ensures a clean baseline through tests. The Skill automates directory selection, preferring `.worktrees` if present, then `worktrees`, and respects any `CLAUDE.md` preferences.

Yes, git worktrees work across Node.js, Rust, Python, and Go projects. The Skill includes per-project setup automation that adapts to each language's build and test conventions, ensuring each worktree maintains a clean baseline.

Avoid worktrees for quick fixes or temporary changes to the current workspace. Worktrees are designed for sustained feature development requiring isolation and clean baselines. For brief edits, branch switching is more appropriate.

The Skill verifies that `.gitignore` includes worktree directories before creating them, preventing accidental commits of isolated workspace artifacts and ensuring repository cleanliness across all linked checkouts.

No, the Skill uses smart directory selection, automatically preferring `.worktrees` if it exists, then `worktrees`, and respecting documented preferences in `CLAUDE.md` for hands-off setup.