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 a properly isolated workspace, detecting existing isolation, preferring native worktree tools, and falling back to manual git worktrees only when necessary. ## 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 Priority: Uses platform-native worktree tools (e.g., EnterWorktree, /worktree commands) when available, falling back to git worktree add only when no native option exists. - Safe Directory Management: Selects .worktrees/ or worktrees/ directories, verifies they are git-ignored before creation, and commits the ignore rule if missing. - Baseline Verification: Auto-detects the project type (Node.js, Rust, Python, Go), installs dependencies, and runs the test suite 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 a worktree, install dependencies, and confirm all tests pass before any code changes begin. ## Quick Start Ask the assistant to set up an isolated git worktree for your new feature branch and verify the project tests pass before starting implementation.
