What problem does it solve? Parallel feature work often requires switching branches or cloning the repository again, and worktrees created inside a repo can be silently committed as gitlinks by auto-committing tools like obsidian-git. This Skill sets up isolated git worktrees with deterministic safety gates that prevent workspace leaks and repository corruption. ## Core Features & Use Cases - External worktree placement: Defaults to a sibling directory (<repo>-wt-<slug>) outside the repository working tree, so no ignore rule is ever needed for isolation. - Safety gates: Gate A detects auto-commit tooling (obsidian-git, hooks, autocommit configs) before creation; Gate B audits parent status and 160000 gitlinks after creation to catch leaks before work begins. - Auto-detected project setup: Runs the right bootstrap (npm install, cargo build, pip install, poetry install, go mod download) based on project files, then verifies a clean test baseline. - Use Case: Before executing an implementation plan, ask the assistant to spin up an isolated worktree; it creates myrepo-wt-feature-x on a new branch, installs dependencies, confirms no gitlink leaks, and reports ready. ## Quick Start Ask the assistant to use the using-git-worktrees skill to create an isolated worktree for your next feature branch before starting implementation.
