using-git-worktrees

Topics in the source

• Using Git Worktrees
• Overview
• Step 0: Detect Existing Isolation
• Step 1: Create Isolated Workspace
• 1a. Native Worktree Tools (preferred)
• 1b. Git Worktree Fallback
• Directory Selection
• Safety Verification (project-local directories only)

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." Before creating anything, check if you are already in an isolated workspace. Submodule guard: GITDIR != GITCOMMON is also true inside git submodules. Before concluding "already in a worktree," verify you are not in a submodule: If GITDIR != GITCOMMON (and not a submodule): You are already in a linked worktree. Skip to Step 2 (Project Setup). Do NOT create another worktree. Report with branch state: On a branch: "Already in isolated workspace at on branch ." Detached HEAD: "Already in isolated workspace at (detached HEAD, externally managed). Branch creation needed at finish time." If GITDIR == GITCOMMON (or in a submodule): You are in a normal repo checkout. Has the user already indicated their worktree preference in your instructions? If not, ask for consent before creating a worktree: "Would you like me to s

This is an excerpt. Refer to the complete source and its current requirements.