What problem does it solve? Feature work done directly in a shared checkout risks contaminating the current branch and mixing unrelated changes. This Skill ensures every implementation task starts 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: Runs git rev-parse checks to determine whether you are already in a linked worktree, a submodule, or a normal checkout before creating anything. - Native Tool Preference: Uses platform-native worktree tools (such as EnterWorktree or a /worktree command) when available, avoiding phantom state the harness cannot manage. - Safe Git Fallback: Selects a worktree directory (.worktrees/ preferred), verifies it is git-ignored, creates the worktree with a new branch, and handles sandbox permission errors gracefully. - Baseline Verification: Auto-detects the project type (Node, Rust, Python, Go), installs dependencies, and runs the test suite to confirm a clean starting point. - Use Case: Before implementing a new API endpoint, invoke this Skill to spin up an isolated worktree on a fresh branch, install dependencies, and confirm all existing tests pass before writing code. ## Quick Start Set up an isolated git worktree for my next feature branch and verify the project tests pass before I start implementing.
