using-git-worktrees

To create an isolated git worktree, the system detects existing linked worktrees and submodules, then uses native worktree tooling or falls back to `git worktree add` with correct directory selection and ignore-safety to establish a sandbox workspace.

Yes, git worktree setup runs project-appropriate dependency installation for Node, Rust, Python, and Go repositories, then executes baseline tests to verify a clean state before you begin implementation.

Using git worktrees is the best way to prevent branch changes from affecting your current checkout, providing an isolated development workspace that avoids disrupting your main branch state.

Yes, you can use `git worktree add` with submodules because the setup process explicitly detects existing linked worktrees and submodules to prevent nested or duplicate worktree creation issues.

You need an isolated git workspace when starting risky refactors or new feature branches, ensuring your main workspace remains clean while preparing a verified baseline before development.

Git worktree handles nested worktrees by detecting if you are already inside a linked worktree, actively avoiding the creation of nested or duplicate worktrees to maintain repository integrity.