worktree

Provision and manage git worktrees for parallel development tracks.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill worktree-mikecubed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/flow/skills/worktree
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill worktree-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage git worktree lifecycle for parallel track execution, reducing friction for flow:parallel-impl.

Core Features & Use Cases

  • Validate preconditions before any worktree is created and detect potential conflicts.
  • Create, verify, and map worktrees and associated branches for each track.
  • Provide a durable cleanup workflow that removes worktrees and prunes references after completion.

Quick Start

Create worktrees for the requested tracks on the specified base branch.

Frequently Asked Questions about worktree

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

FAQPage Schema
How do I create git worktrees for parallel development tracks in a single repository?

Creating git worktrees for parallel development tracks requires validating preconditions first, then provisioning isolated worktrees with associated branches and generating a manifest to map each track to its directory.

What is the best way to manage git branch isolation for parallel workflows without cloning?

Git worktree branch isolation allows multiple parallel workflows to operate in a single repository by creating separate working directories with dedicated branches, verifying each setup, and detecting conflicts before execution begins.

Can I detect branch conflicts before creating a git worktree?

Yes, precondition validation checks for potential conflicts before any git worktree is created, ensuring that parallel branch management tracks do not interfere with each other during isolated workflow execution.

How do I clean up git worktrees and prune references after parallel execution finishes?

Cleaning up git worktrees after parallel execution involves a durable lifecycle workflow that removes the worktree directories and prunes dangling branch references to keep the repository clean.

Does this worktree orchestration require any special dependencies or external components?

No external dependencies or components are required for worktree orchestration, as the skill handles branch management, conflict detection, and lifecycle cleanup entirely through internal precondition validation and git operations.