using-git-worktrees

To create isolated git workspaces, you can create git worktrees that set up separate directories for feature development. This prevents workspace contamination and accidental commits by keeping new branches in their own isolated working directories.

To keep git worktree directories untracked, verify the path using git check-ignore and automatically update the .gitignore file. The directory selection prioritizes .worktrees, then worktrees, or uses a global config path to prevent accidental commits.

To automatically run dependency setup, the worktree creation process detects project tooling files like package.json, Cargo.toml, pyproject.toml, or go.mod. It then auto-runs the appropriate dependency install command for the detected project type.

Verifying a clean test baseline before feature work ensures the isolated git worktree has a functional starting state. Running the test suite confirms the automated setup succeeded and prevents attributing pre-existing failures to your new feature changes.

Yes, you can use git worktrees to prepare isolated environments for agent-driven tasks and tests. This workflow creates a separate workspace where automated agents can safely execute implementation plans without risking your primary working directory.