using-git-worktrees

What problem does it solve? Feature work done directly in your main checkout risks polluting your current branch and mixing unrelated changes. This Skill ensures every implementation task starts in an isolated workspace, using your platform's native worktree tools when available and falling back to manual git worktrees otherwise. ## Core Features & Use Cases - Isolation Detection: Checks whether you are already inside a linked worktree or a git submodule before creating anything, avoiding duplicate or phantom workspaces. - Native Tool Preference: Uses harness-provided worktree tools (e.g. EnterWorktree, /worktree commands) first, falling back to git worktree add only when no native tool exists. - Safe Directory Handling: Selects .worktrees/ or worktrees/ directories, verifies they are git-ignored, and commits a .gitignore fix if not. - Use Case: Before implementing a new feature branch, the Skill sets up an isolated worktree, installs project dependencies (npm, cargo, pip, go), and runs the test suite to confirm a clean baseline. ## Quick Start Set up an isolated git worktree for my new feature branch and verify the project tests pass before I start implementing.