fleet-managing-worktrees

Git worktrees for parallel Claude sessions are managed by automating the creation, fan-out, and cleanup of isolated working trees. This ensures each session operates independently without disturbing the primary checkout.

Reviewing multiple open PRs locally is supported by fanning out one worktree per open pull request. This allows parallel PR reviews across isolated working trees without affecting your main repository checkout.

Cleaning up spent git worktrees after merges involves pruning trees with nothing left to land. This targets clean trees whose branches were deleted upstream or are fully merged into the remote default branch.

Creating a new task worktree requires specifying a task name to generate a dedicated working tree beside your main checkout. This tree is based on the remote default branch to ensure a clean starting point.

Pruning stale git worktrees includes safeguards to avoid deleting unpushed or in-use trees. The cleanup process only removes spent worktrees that have nothing left to land, preventing accidental data loss.

Using parallel worktrees for PR review requires a git repository with a defined remote default branch. The automation depends on identifying open PRs and establishing isolated working trees based on that upstream branch.