using-git-worktrees

Isolate feature branches in git worktrees by creating a dedicated workspace directory, ensuring paths are gitignored, and running project setup plus baseline tests. This prevents feature development from polluting your current workspace and verifies a clean starting baseline.

The best way to set up an isolated git workspace is using git worktrees to spawn branch-specific directories. The process honors existing `.worktrees` folders or CLAUDE.md preferences, auto-installs dependencies across Node or Python, and confirms baseline tests pass.

Git worktree workspace isolation supports multiple programming language environments. During setup, it automatically detects and installs dependencies across Node, Rust, Python, and Go projects before running baseline tests to confirm environment readiness.

You need to verify safe directories before creating a new git worktree to ensure project-local paths are properly gitignored. This verification step prevents accidental commits of workspace artifacts and guarantees the feature branch starts from a clean, non-polluted baseline.

Manage directory selection for isolated git worktrees through priority-driven logic that reuses existing `.worktrees` or `worktrees` directories, honors CLAUDE.md preferences, and prompts the user for input when no established location is found in the repository.

Feature branch worktrees require running baseline tests to confirm environment readiness. After creating the isolated workspace and installing dependencies, the workflow executes baseline tests to verify the clean environment before you begin executing your implementation plan.