using-git-worktrees

Create isolated git worktrees and branches for parallel agent tasks.

139|7|Updated May 8, 2026
One-click install
npx skills add https://github.com/arbiterForge/codeArbiter --skill using-git-worktrees-arbiterforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-git-worktrees
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/using-git-worktrees
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill using-git-worktrees-arbiterforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents parallel agent work from colliding by giving each unit its own isolated git worktree, branch, and filesystem boundary. It is designed for opt-in concurrency when multiple tasks must run safely without touching one another or the default path.

Core Features & Use Cases

  • Per-unit isolation: Creates one worktree per parallel task so concurrent edits stay separated.
  • Controlled integration: Folds accepted work back onto the caller's working branch instead of finishing each unit independently.
  • Cleanup discipline: Removes created worktrees and clears the scratch manifest after the work is integrated or abandoned.
  • Use case: Run several autonomous implementation or review units at once while preserving a single commit gate and a single branch finish at the end.

Quick Start

Ask the assistant to set up isolated git worktrees for your explicitly approved parallel tasks and then integrate the accepted results back onto your current working branch.

Frequently Asked Questions about using-git-worktrees

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

FAQPage Schema
How do I prevent parallel agents from colliding on the same git branch?

Git worktree isolation prevents parallel agents from colliding by creating a separate worktree and branch for each task unit. This ensures concurrent edits stay separated without touching the default working path.

What is the best way to run multiple autonomous development tasks at once?

Running multiple autonomous tasks requires opt-in concurrency with isolated git worktrees. Each unit gets its own filesystem boundary and branch, allowing parallel execution while preserving a single commit gate.

How do I merge isolated git worktrees back into my working branch?

Merging isolated git worktrees back into your working branch is handled through controlled integration. The accepted work from each worktree is folded onto the caller's working branch instead of finishing each unit independently.

Do I need explicit approval to set up task isolation for parallel agents?

Explicit isolation approval is required to set up task isolation for parallel agents. You must provide a per-task unit list and enable manifest tracking before the worktree creation process begins.

How do I clean up git worktrees after integrating parallel tasks?

Cleaning up git worktrees after integration requires complete teardown of every created worktree. The scratch manifest is cleared and all worktrees are removed once the work is successfully integrated or abandoned.

When should I not use git worktree branch isolation for subagent execution?

Git worktree branch isolation should not be used for subagent execution without opt-in concurrency. It is specifically designed for dispatching multiple work units that must stay separate and requires branch-safe integration overhead.