using-git-worktrees

Git worktree isolation creates a separate linked working directory for your branch, allowing you to start risky feature implementations without polluting your current checkout. The Skill detects existing isolation, uses native worktree tools when available, or falls back to manual git worktree creation with guardrails.

To prevent feature work from disturbing your current git checkout, use a linked git worktree. This Skill detects whether you are already in an isolated worktree or submodule, then uses native worktree tooling or a git fallback to create a separate working directory for your branch.

Yes, you can run baseline tests automatically. After creating the isolated git worktree, the Skill installs project dependencies and runs the baseline test suite to validate the environment, ensuring your workspace is ready before you begin editing code.

Git worktree creation checks for existing isolation first. If you are already inside a linked worktree or a submodule, the Skill detects this state before taking action, preventing duplicate workspace setup and avoiding nested directory conflicts during feature branch isolation.

If native worktree tooling is unavailable, the Skill falls back to manual git worktree creation. This fallback applies ignore verification, sandbox-aware directory handling, and directory selection rules to safely isolate the workspace for your feature branch.