What problem does it solve? Working in linked Git worktrees often fails in subtle ways: full test baselines break for reasons outside your task, sandboxed runtimes silently block edits to a worktree root, and fresh worktree virtualenvs race or miss dependencies. This Skill provides the operational checks to confirm a worktree is actually editable, testable, and correctly isolated before you commit work to it. ## Core Features & Use Cases - Scoped Baseline Gate: Establishes a documented, user-approved partial test baseline when the full suite fails for pre-existing, out-of-scope reasons, while still reporting both results. - Declared-Root Routing & Edit Preflight: Inspects the runtime's writable-root policy on Windows or sandboxed environments, routes work to a correctly rooted task when the worktree is not writable, and verifies edit/index/test operations with a disposable preflight file. - Venv & File-Discovery Readiness: Documents uv sync concurrency races, source-only dependency build failures (e.g. petls), gitignore-blind Glob/Grep behavior inside worktrees, and workarounds for contract checks that are not worktree-venv-safe. - Use Case: You create a linked worktree on Windows to implement a feature, but edits fail and the full pytest baseline errors on an unrelated optional dependency. Use this Skill to verify the writable-root policy, run the edit-path preflight, scope the baseline with explicit approval, and deliver with evidence that all operations resolved inside one worktree. ## Quick Start Use the using-git-worktrees-extras skill to validate that my linked worktree is writable and establish a scoped test baseline before I start implementation.