using-git-worktrees

To create an isolated Git worktree, the tool provisions a separate branch-backed workspace, validates directory ignore rules, runs language-specific dependency installation, and executes baseline tests before signaling readiness. This prevents contaminating your main checkout while establishing a clean development baseline.

Using Git worktrees is the best way to manage multiple branches without switching, as it creates isolated directory-level workspaces for parallel agent work or feature implementation. This approach reduces merge conflicts and prevents accidental commits to the main repository checkout.

Yes, the Git worktree automation handles dependency installation by running language-specific setups for Node, Rust, Python, and Go projects. After creating the isolated workspace, it automatically detects the project language and executes the appropriate dependency installation commands before running baseline tests.

You can use a custom directory for Git worktrees by providing a global location or specifying a preference in CLAUDE.md. The tool follows priority rules, preferring local .worktrees or worktrees directories first, then falling back to your user-provided global location for workspace creation.

If baseline tests fail after creating a Git worktree, the tool reports the failing tests or issues and asks whether to proceed or abort. This failure handling mechanism prevents blind continuation on broken baselines, ensuring you confirm readiness before starting feature development in the isolated workspace.

You need to update .gitignore before creating a Git worktree to ensure project-local worktree directories are properly ignored by Git. The tool verifies ignore validation, updates .gitignore if necessary, and commits the change to prevent the isolated workspace directories from being accidentally tracked in your repository.