using-git-worktrees

Git worktrees create isolated workspace directories linked to a single repository, allowing safe feature development without altering your current project state. This skill automates worktree creation, detects existing isolation, and verifies your baseline setup before integrating changes.

The best way to set up an isolated dev environment is using native workspace tools when available, falling back to git worktrees when needed. This approach ensures safe experimentation by establishing a separate workspace that prevents changes to the main project baseline.

Yes, this git worktree workflow uses consent-based workspace creation to ensure you explicitly approve the establishment of a new isolated environment. It detects if you are already working in an isolated workspace and skips creation to avoid duplicate or unwanted worktrees.

Yes, you can run baseline checks and tests in a git worktree before merging changes. After setting up the isolated workspace, this skill performs optional setup and test verification steps to ensure your feature work is stable before you integrate it back into the main repository.

You should fall back to git worktrees when native workspace isolation tools are unavailable or unsupported by your current repository environment. This skill prefers native tooling first to minimize overhead, only establishing a git worktree when needed to guarantee a safe, isolated development context.