using-git-worktrees

Creating a Git worktree involves checking existing directories (.worktrees or worktrees), reading CLAUDE.md for preferences, and prompting for a location. The process ensures worktrees are ignored by Git and baseline tests pass before use.

Using Git worktrees keeps feature work isolated from your main workspace. The system auto-detects the project name, creates a worktree with the correct branch, runs project setup, and reports a clean baseline ready for development.

Yes, the worktree creation workflow includes safe creation steps like git ignore verification and baseline test validation. It ensures tests pass in the new worktree before proceeding with feature work.

Yes, you can configure directory preferences for Git worktrees using CLAUDE.md. The system prioritizes existing directories like .worktrees, then checks CLAUDE.md, and finally prompts the user when ambiguity remains.

The worktree setup runs project setup automatically for common ecosystems. It auto-detects the project name, creates the worktree with the correct branch, and executes the necessary setup commands to prepare the environment.

Git worktrees are ideal when you need to isolate feature work without polluting the main workspace or cloning the entire repository. They provide a clean baseline by creating linked working trees with correct branches and verified ignored paths.