worktree-management

The Parallel Claude sessions rule in CLAUDE.md mandates worktrees for branch work. This skill is the helper that makes that ergonomic — three modes, surgical, no auto-cleanup of work you didn't make.

When to use

• Starting a task that needs a branch. Spawn a worktree instead of git checkout-ing in the primary checkout.
• Reviewing all open PRs locally. One worktree per PR, lined up under ../<repo>-pr-<num>/ so multiple Claude sessions can each take one.
• Cleaning up stale worktrees after PRs merge or branches get deleted upstream.

Never use this skill to remove a worktree that has uncommitted work — the Don't leave the worktree dirty rule applies; the dirty worktree is held intentionally until its owner commits.

Modes

Mode 1 — new <task-name> (default)

Spawn a new worktree at ../<repo>-<task-name>/ based on the remote's default branch.