What problem does it solve? Starting feature work directly in your main checkout risks polluting your current branch, mixing unrelated changes, and losing track of experiments. This Skill ensures every implementation task runs in an isolated workspace, either through your platform's native worktree tooling or a manual git worktree fallback. ## Core Features & Use Cases - Isolation Detection: Checks whether you are already inside a linked worktree by comparing git directory paths, preventing nested or duplicate worktrees. - Native Tool Preference: Uses platform-provided worktree tools (like EnterWorktree or /worktree commands) when available, falling back to git worktree add only when necessary. - Safe Directory Conventions: Follows a priority order for worktree placement (explicit instructions, existing .worktrees/ or worktrees/ directories, then default) and verifies the directory is git-ignored before creation. - Clean Baseline Verification: Runs project setup and the test suite to confirm the workspace starts green before implementation begins. - Use Case: Before implementing a new API endpoint, activate this Skill to spin up an isolated worktree on a fresh branch, install dependencies, and verify tests pass, keeping your main checkout untouched. ## Quick Start Set up an isolated git worktree for my new feature branch and verify the test baseline is clean before I start coding.
