using-git-worktrees

Git worktrees prevent workspace contamination by creating a dedicated directory that shares the repository but keeps feature branch changes separate. This allows safe experimentation across project directories without affecting the main workspace.

Using git worktrees is the best way to manage multiple branches without switching context in a single directory. You can develop a new feature on a separate branch while maintaining a clean main workspace and ready-to-run tests.

To set up a safe git worktree for local development, the tool enforces directory selection priority, verifies the target directory is ignored by git to prevent accidental commits, and optionally runs project setup steps for Node.js, Rust, Python, or Go environments.

Yes, git worktree setup works with Node.js, Rust, Python, and Go project environments. After creating the isolated worktree, it automatically runs the appropriate setup steps required to prepare your specific development environment.

To ensure your git worktree directory is not accidentally committed, the setup performs safety verification by checking gitignore rules. It prefers existing hidden directories like .worktrees and confirms the chosen location is properly ignored before creating the worktree.

Yes, you can use CLAUDE.md preferences to configure git worktree directory locations. The directory selection priority checks for an existing hidden .worktrees folder, then a worktrees folder, then consults CLAUDE.md, before prompting you to choose a location.