using-git-worktrees

To create git worktrees, the workflow detects existing project-local .worktrees directories and sets up isolated branch checkouts safely. It enforces .gitignore checks to prevent committing worktree contents, configures the new worktree, and validates the setup before switching into it.

Using git worktrees is the best way to manage multiple branches simultaneously, as each worktree provides an isolated directory for a single branch. This avoids stashing or switching branches repeatedly in one workspace, keeping parallel feature development clean and separate.

Creating a git worktree does not modify your .gitignore but enforces safety checks against it before creation. This validation step ensures worktree directories are properly ignored, preventing you from accidentally committing the worktree contents into the main repository.

You can specify a custom directory location for git worktrees, or the workflow will prefer a project-local .worktrees folder if it exists. It respects CLAUDE.md preferences for target locations and prompts you for a path when no preference is defined.

Git worktrees share the same repository history without duplicating the entire .git directory, making them more efficient than cloning. They provide safe isolation for parallel branching while honoring existing directories and allowing optional project setup commands to run automatically.

You should not use git worktrees if your .gitignore configuration does not properly exclude the target worktree directory, as the safety checks will flag this risk. The workflow validates this precaution to prevent accidentally committing isolated worktree contents.