Skip to content

vt-c-git-worktree

[DEPRECATED] Superseded by Claude Code's built-in worktree feature (.claude/worktrees/). Kept only for repositories that still hold worktrees created by its retired manager script; do not use it for new work.

Plugin: vt-base
Category: Tooling
Command: /vt-c-git-worktree

Git Worktree Manager — deprecated

This skill is deprecated (SPEC-202, 2026-09-16) and will be removed at the next MAJOR.

Spec worktrees are created with the built-in worktree feature only. /vt-d-activate classifies the working copy itself and offers EnterWorktree; no skill or command routes spec work here any more. worktree-manager.sh remains on disk, unchanged, for repositories that still hold worktrees it created — the retirement checklist is intake/pending/spec-202-followup-retire-git-worktree.md.

Use the built-in feature instead

  • Where worktrees live: .claude/worktrees/<name>, one per working copy, created and entered by the EnterWorktree tool (CLI equivalent: claude --worktree <name>; in Claude Desktop, start a session with worktree isolation).
  • What they branch from: the worktree.baseRef setting — fresh (default) branches from the origin default branch, head from the invoking checkout's local HEAD. No mode checks out a named existing branch, which is why /vt-d-activate renames the auto-named branch instead.
  • Gitignored files: a worktree is a fresh checkout, so .env and friends do not travel with it. List the gitignored paths that should be copied into new worktrees in the project's .worktreeinclude.

For the conventions around several worktrees at once — which one holds main, where merges happen, how to avoid two working copies for one spec — see vt-c-using-git-worktrees and docs/solutions/patterns/v025-multi-worktree-workflow.md.

Next actions

  1. Starting spec work? Run /vt-d-activate SPEC-NNN and follow its workspace check — it creates or enters the built-in worktree for you.
  2. Holding a worktree this skill's script created? Finish or migrate that work; the script is unchanged during the deprecation window, but nothing new should be created with it.
  3. Writing or reviewing toolkit docs? Point readers at the built-in feature, never at this skill or its script.