worktree

zuvo:worktree

Git worktree isolation with structured completion options.

Three modes: CREATE (set up a new worktree), FINISH (wrap up work in the current worktree), and PRUNE (reclaim finished worktrees and fix a nested layout).

Detect mode automatically:

• If the user explicitly says "create", "finish", or "prune"/"cleanup", honor that regardless.
• If the current directory IS inside a worktree (check git worktree list), default to FINISH.
• If the current directory is the main checkout, default to CREATE.

---

CREATE Mode

Step 0: Accumulation Precheck

Run PRUNE steps 1-2 (bookkeeping reconcile + classification) in report-only form. Removing nothing, print one line:

Worktrees in this repo: <n> live (<n> reclaimable, <n> idle >30d). Layout: <sibling | NESTED>.

If reclaimable or nested worktrees exist, point at zuvo:worktree prune and continue with CREATE. Never block CREATE on cleanup.

Step 1: Determine Worktree Directory

Compute the default first -- it is a sibling of the repo, never a child:

REPO_ROOT=$(git rev-parse --show-toplevel)
REPO_NAME=$(basename "$REPO_ROOT")
DEFAULT_WTDIR="$(dirname "$REPO_ROOT")/${REPO_NAME}-worktrees"

Resolution order. Use the first match, do NOT ask the user:

1. $ZUVO_WORKTREE_DIR if set -- absolute path, or relative to $REPO_ROOT.
2. Project instructions preference -- a worktree/worktrees section in the project AGENTS.md or CLAUDE.md that declares a directory. If the declared path is inside $REPO_ROOT, honor it but emit the nested-layout warning below.
3. Existing sibling -- $DEFAULT_WTDIR already exists.
4. Existing nested directory (LEGACY) -- .worktrees/, worktrees/, or .claude/worktrees/ inside $REPO_ROOT. Use it so worktrees for one repo do not end up split across two locations, but you MUST emit the nested-layout warning and offer the PRUNE-mode migration in the same turn.
5. Default -- $DEFAULT_WTDIR. Create it with mkdir -p.