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 (with a submodule guard) 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 (explicit preference > existing .worktrees/ or worktrees/ > default .worktrees/) 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 executing an implementation plan, ask the assistant to set up an isolated workspace; it detects your environment, creates the worktree safely, installs dependencies, and confirms tests pass. ## Quick Start Ask the assistant to set up an isolated worktree for your new feature branch and verify the project tests pass before starting work.
