worktree-manager

Orchestrate parallel git worktrees with deterministic port allocation and merge coordination.

Updated Mar 19, 2026

Search Tags:#ai #orchestration #worktree #parallel #spawn #merges #scopes

Ready to run

npx skills add https://github.com/espensev/ai-skills --skill worktree-manager-espensev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree-manager
Source: https://github.com/espensev/ai-skills/tree/main/claude-skills/skills/worktree-manager
Command: npx skills add https://github.com/espensev/ai-skills --skill worktree-manager-espensev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates parallel AI agent worktrees to enable isolated development and deterministic coordination. This tool lets teams run multiple development streams in parallel without interfering with each other, while providing guardrails for safe coordination and clean handoffs.

Core Features & Use Cases

Spawn and manage isolated git worktrees for concurrent agent development with deterministic port allocation.
Coordinate merges in smallest-diff-first order to minimize conflicts and preserve branch history.
Safely teardown worktrees with scope validation and state verification to prevent data loss.

Quick Start

Spawn a basic parallel worktree set with non-overlapping scopes and bootstrap.

Frequently Asked Questions about worktree-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run parallel AI agents in isolated git worktrees without conflicts?▼

Parallel AI agents run in isolated git worktrees by spawning independent workspaces with non-overlapping file scopes and deterministic port allocation, preventing conflicts during concurrent feature development and testing.

What is the best way to coordinate merges across multiple parallel development streams?▼

Coordinating merges across parallel development streams is handled using a smallest-diff-first merge strategy, minimizing conflicts and preserving branch history during multi-agent campaigns across repositories.

How do I safely teardown a git worktree after parallel development is complete?▼

Safely tearing down a git worktree requires scope validation and state verification to prevent data loss, ensuring the isolated development workspace is cleanly removed without affecting other parallel streams.

Can I assign non-overlapping file scopes to concurrent development streams?▼

Concurrent development streams can be assigned non-overlapping file scopes using the scope command, ensuring multiple AI agents work on isolated sections of the repository without interfering with each other.

How does deterministic port allocation work for parallel agent worktrees?▼

Deterministic port allocation for parallel agent worktrees assigns fixed, non-colliding network ports to each isolated workspace, enabling concurrent testing and development streams to run simultaneously without network conflicts.

When do I need parallel worktree orchestration for multi-agent campaigns?▼

Parallel worktree orchestration is needed when running multi-agent campaigns across repositories that require isolated development, concurrent feature work, and coordinated merges with safe guardrails for clean handoffs.