What problem does it solve? Working on multiple branches simultaneously or running parallel agent sessions risks clobbering your current checkout, mixing unrelated changes, and losing work to branch collisions. This Skill sets up isolated git worktrees so each feature or session gets its own workspace sharing the same repository. ## Core Features & Use Cases - Smart Directory Selection: Follows a priority order (existing .worktrees/ or worktrees/, then CLAUDE.md preference, then asks the user) so worktrees land where the project expects them. - Safety Verification: Verifies project-local worktree directories are git-ignored before creation, and auto-detects project setup (npm, Cargo, pip, Poetry, Go) plus runs baseline tests before handing off the workspace. - Jira-Aware Branching: Derives branch names from linked Jira issue keys (e.g., IEO-121) and bases them on parent epic branches when present. - Use Case: Before implementing a feature from a plan document, spin up .worktrees/IEO-121 on the correct base branch, install dependencies, confirm tests pass, and start coding without touching your main checkout. ## Quick Start Use the using-git-worktrees skill to set up an isolated workspace for the current feature branch.
