using-git-worktrees

To create an isolated git worktree, the tool sets up a separate workspace, selects a directory like .worktrees, verifies it is git-ignored, creates the branch, runs dependency setup, and validates tests before reporting readiness.

Git worktree directories get tracked when they are not listed in .gitignore. This tool enforces safety verification, automatically adding and committing .gitignore entries for project-local locations to prevent tracking worktree contents.

The best way to run parallel branches safely is using isolated git worktrees. This approach provides separate development workspaces, preventing accidental repository pollution and costly context switching between concurrent feature branches.

Yes, you can auto-run dependency setup when creating a git worktree. The tool automatically executes project setup commands like npm install, pip/poetry, cargo build, or go mod download after creating the worktree.

To verify a clean test baseline in a new git worktree, the tool automatically executes project tests immediately after creating the worktree and running dependency setup, reporting readiness only when tests pass.

Directory selection priority matters for organizing git worktrees. The tool prefers the .worktrees directory, falls back to worktrees, respects CLAUDE.md preferences, or prompts the user to ensure proper project-local or global placement.