using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Using Git Worktrees Overview Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools. Fall back to manual git worktrees only when no native tool is available. Core principle: Detect existing isolation first. Then use native tools. Then fall back to git. Never fight the harness. Announce at start: "I'm using the using-git-worktrees skill to set up an isolated workspace." Step 0: Detect Existing Isolation Before creating anything, check if you are already in an isolated workspace. bash GITDIR=$(cd "$(git rev-parse --git-dir)" 2/dev/null && pwd -P) GITCOMMON=$(cd "$(git rev-parse --git-common-dir)" 2/dev/null && pwd -P) BRANCH=$(git branch --show-current) Submodule guard: GITDIR != GITCOMMON is also true inside git submodules. Before concluding "already in a worktree," verify you are not in a submodule: bash If this returns a path, you're in a submodule, n…