using-git-worktrees

You can create an isolated Git worktree by automating directory discovery across local or global paths, verifying gitignore rules, and running project setup steps to ensure a safe, clean baseline for your feature branch.

Git worktrees provide isolation by sharing the repository history while keeping file changes separate, preventing pollution of your main working directory and allowing safer, clean experimentation on feature branches.

Yes, safety verification checks gitignore rules before creating a local worktree in directories like .worktrees, guiding you to add ignores if needed to prevent tracking unwanted files.

Yes, auto-setup detects the project name and runs setup steps like npm, cargo, or pip, followed by test-baseline validation to verify a clean baseline before you start working in the worktree.

Directory discovery selects a worktree location using defined priority across project-local directories like .worktrees or worktrees, and global paths, applying automatic baseline verification to ensure consistency.

You should avoid isolated Git worktrees if your project lacks clear gitignore rules for the target directories, or if test-baseline validation fails, as the safety checks depend on a clean baseline.