worktree

Create isolated git worktrees for parallel bead execution.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cmtkdot/arc --skill worktree-cmtkdot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/cmtkdot/arc/tree/main/skills/worktree
Command: npx skills add https://github.com/cmtkdot/arc --skill worktree-cmtkdot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Worktree-based isolation solves parallel bead execution conflicts by providing dedicated, branch-scoped workspaces that share a common Git object store but avoid interfering file edits.

Core Features & Use Cases

  • Isolated worktree per bead to prevent cross-bead file conflicts.
  • Standardized naming conventions and lifecycle management for beads.
  • Safety verification and controlled merge-back to the baseline.
  • Support for project-local or external worktrees and automated setup.

Quick Start

Create a dedicated worktree and start a bead run to isolate execution and prevent file conflicts.

Frequently Asked Questions about worktree

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

FAQPage Schema
How do I prevent file conflicts during parallel git worktree execution?▼

Git worktree isolation prevents parallel execution file conflicts by providing dedicated, branch-scoped workspaces that share a common Git object store but avoid interfering file edits during concurrent runs.

What is the best way to manage multiple git worktree lifecycles for parallel runs?▼

Managing multiple git worktree lifecycles involves standardized naming conventions, automated discovery, and controlled cleanup scripts to safely isolate execution and prevent cross-bead file conflicts.

How does git worktree branch management handle safe merge-back to the baseline?▼

Git worktree branch management handles safe merge-back by applying safety verification checks before merging the isolated branch-scoped workspace changes back to the main baseline repository.

Can I use external worktrees for parallel pipeline execution?▼

Yes, you can use external worktrees for parallel pipeline execution, as the lifecycle management supports both project-local and external directory setups to isolate runs.

Do I need separate git object stores for each isolated worktree?▼

No, you do not need separate git object stores; isolated worktrees share a common Git object store while maintaining separate branch-scoped working directories to prevent file conflicts.

When should I not use git worktrees for isolated execution?▼

You should avoid git worktrees for isolated execution if your parallel runs require completely separate repository histories, as this approach relies on a shared Git object store to function efficiently.