What problem does it solve? Feature work done directly in a shared checkout risks contaminating the current branch and mixing unrelated changes. This Skill guarantees every implementation task starts in an isolated workspace, using the platform's native worktree tooling when available and falling back to manual git worktrees otherwise. ## Core Features & Use Cases - Isolation Detection: Detects whether you are already inside a linked worktree or a git submodule before creating anything, avoiding nested or duplicate workspaces. - Native Tool Preference with Git Fallback: Uses harness-native worktree tools (e.g., EnterWorktree, /worktree commands) first, and only runs git worktree add when no native tool exists, with directory priority rules and .gitignore safety verification. - Baseline Verification and CI Gate: Auto-detects the project stack (Node, Rust, Python, Go), installs dependencies, runs the test suite for a clean baseline, and invokes the ci-pipeline-setup skill if no CI configuration exists. - Use Case: Before implementing a new feature, ask the agent to set up an isolated workspace; it creates .worktrees/my-feature, installs dependencies, confirms tests pass, and reports the workspace is ready. ## Quick Start Set up an isolated git worktree for my new feature branch and verify the test baseline is clean before I start implementing.
