using-git-worktrees

Create an isolated workspace for feature work by detecting existing isolation and establishing a new one using native tools. If native tooling is unavailable, fall back to manual git worktrees to protect your current branch state.

A git worktree provides workspace isolation for feature work by allowing multiple working directories from a single repository. It protects your current branch state and prevents workflow conflicts during concurrent development.

Git worktrees should avoid submodules because they complicate workspace isolation and can cause conflicts. The workspace setup checks for submodules and prevents workspace creation if they are detected to ensure a clean environment.

Protect your current branch by using an isolated workspace that coordinates branch state preservation. Verify the workspace is clean before starting feature work, ensuring your main workflow remains completely undisturbed.

Set up project dependencies in a new git worktree by performing baseline checks and project setup steps inside the isolated workspace. This reproducible setup includes installing dependencies, building, and running tests before implementation.

Avoid using git worktrees when your project contains submodules, as they interfere with workspace isolation. Additionally, if an isolated workspace already exists, creating another one is unnecessary and prevented by consent checks.