using-git-worktrees

Git worktrees isolate development work by creating separate working directories linked to the same repository, preventing cross-branch contamination. This enables parallel experimentation without switching branches in your primary workspace.

Safe git worktree setup requires verifying the worktree directory is ignored by gitignore to prevent repository pollution. You should also perform baseline validation and apply automated setup steps before switching branches.

Managing git worktree locations uses priority-based selection, defaulting to a project-local .worktrees directory with automatic fallback to a global location. You can optionally use CLAUDE.md directives to guide the choice.

Yes, guided creation and setup steps support both local and global git worktrees. The process includes safety verification, baseline validation, and optional CLAUDE.md preferences to steer the worktree location automatically.

Verifying gitignore before creating a git worktree ensures the isolated workspace directory is ignored by git, preventing cross-branch contamination and keeping the main repository clean from untracked worktree files.

Git worktrees are not ideal if your project lacks proper gitignore support for the worktree directory or if baseline validation fails, as this risks polluting the main repository with untracked development files.