using-git-worktrees

Git worktrees isolate feature development by creating a separate linked workspace, preventing accidental changes to your primary branch while allowing dependency installation and baseline tests to run cleanly.

Running baseline tests in an isolated Git worktree ensures a clean environment by installing dependencies from the manifest first, verifying the canonical test suite passes before you implement any new feature code.

Git worktree creation handles submodules correctly by applying native worktree tooling or falling back to `git worktree add`, ensuring linked worktrees and their submodule dependencies are properly initialized across the isolated workspace.

Yes, Git worktree creation detects existing isolation first to prevent nested or redundant worktrees, checking whether you are already inside a linked worktree before attempting to add a new isolated directory.

When sandbox permission failures occur during `git worktree add`, the process applies directory-priority selection and ignore verification for project-local paths to safely handle the fallback workspace creation.

Yes, the process prefers native worktree tools when available to create the workspace safely and consistently, only falling back to manual `git worktree add` commands with guardrails if native tooling is absent.