using-git-worktrees

Use git worktrees to create isolated feature workspaces that prevent main repository contamination. The process performs prioritized directory selection, creates worktrees tied to branch names, runs project setup, and verifies a clean test baseline.

Git worktree directory selection respects project conventions by using a priority system: hidden project-local locations first, then visible project-local locations, and finally global locations. This ensures worktrees are placed according to existing project structure.

To ensure worktree directories are not accidentally committed, safety verification enforces gitignore rules for project-local worktree directories. It provides automatic remediation by adding and committing .gitignore changes, along with clear reporting to prevent accidental commits.

Yes, when creating a git worktree, the setup process is project-aware and auto-detects dependencies. It automatically runs installs and builds for Node, Python, Rust, and Go environments within the newly created isolated workspace.

Yes, baseline test verification runs within the isolated git worktree to confirm a clean starting point before feature implementation begins. This ensures the newly created workspace has a verified, reproducible environment prior to development.

The best way to manage parallel feature workspaces is using git worktrees for workspace isolation. This allows developers to create separate branches, run project setup in parallel worktrees, and keep feature work completely separated from the main repository.