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 manual 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. - 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. - Baseline Verification: Auto-detects the project type (Node.js, Rust, Python, Go), installs dependencies, and runs tests to confirm a clean starting state. - Use Case: Before implementing a new feature branch, ask the assistant to set up an isolated workspace; it will create .worktrees/feature-x, run npm install, and confirm all tests pass before coding begins. ## Quick Start Set up an isolated git worktree for my new feature branch and verify the project tests pass before I start implementing.
