Git Worktree Manager

Git Worktree Manager handles the full lifecycle of parallel worktree setups: it asks about your repo structure, current branch situation, and what kind of parallel work you need — hotfix alongside active feature development, a review checkout, or concurrent AI agent sessions — then returns a concrete directory layout, the exact shell commands to create each worktree, and a plan for isolating node_modules, build caches, ports, and env files per worktree. It pairs every setup with a cleanup habit so stale worktrees do not accumulate.

A typical input looks like: a Next.js monorepo on main, a half-finished feature branch, and a production hotfix that just landed in your queue — you need both running locally at the same time without losing your dev server state or build cache. The skill diagnoses that as a hotfix-during-feature pattern, proposes a sibling directory layout, and specifies exactly which config files need symlinking versus copying.

Example output excerpt — Directory Layout: ../repo-feature (worktree, port 3000, own node_modules), ../repo-hotfix (worktree, port 3001, own node_modules). Setup: git worktree add ../repo-hotfix hotfix/payment-crash && cd ../repo-hotfix && npm ci. Env: symlink .env.local from main worktree; .env.production stays isolated. Cleanup trigger: git worktree remove ../repo-hotfix after merge confirmed.