What problem does it solve? Starting feature work directly in your main checkout risks polluting your current branch and mixing unrelated changes. This Skill ensures every implementation task begins in an isolated workspace, detecting existing isolation first and falling back to git worktrees only when no native tool exists. ## Core Features & Use Cases - Isolation Detection: Checks whether you are already inside a linked worktree or a submodule before creating anything, preventing nested worktrees. - Native Tool Preference: Defers to platform-native worktree tools (e.g., EnterWorktree) and only uses git worktree add as a fallback, avoiding phantom state the harness cannot manage. - Safe Directory Selection: Follows a priority order for worktree placement (existing .worktrees/, legacy global path, declared preference, default) and verifies the directory is git-ignored before creation. - Use Case: Before implementing a new feature, the Skill sets up .worktrees/feature-x, runs npm install or the appropriate project setup, executes the test suite to confirm a clean baseline, and reports the workspace is ready. ## Quick Start Ask the assistant to set up an isolated worktree for your next feature using the using-git-worktrees skill before writing any code.
