using-git-worktrees

To create an isolated Git worktree, the skill automates directory selection, verifies gitignore rules, branches from origin/main, and runs environment setup. This process prevents cross-branch contamination while preserving a clean main workspace for your features.

Git worktree directory selection follows a priority sequence: it prefers project-local .worktrees, then a general worktrees folder, then CLAUDE.md hints, and finally prompts you. It verifies the chosen path is ignored by gitignore to ensure safety.

Yes, the worktree setup auto-detects project tooling for Node.js, Rust, Python, and Go environments. It automatically runs the appropriate setup steps for your detected stack, ensuring the new worktree is ready for development immediately.

Using isolated Git worktrees is the best way to prevent cross-branch contamination. By creating separate directories for features and verifying a clean baseline with tests, the workflow ensures your main repository remains unpolluted during development.

You need to ensure your chosen worktree directory is ignored by gitignore rules. The skill verifies this safety requirement and guides you through necessary gitignore updates if the directory is not currently ignored.

Running tests after creating a Git worktree performs a clean baseline verification. This ensures the new worktree starts from a stable state, confirming the automatic environment setup completed successfully before you begin feature development.