git-worktrees

Create isolated Git worktrees for parallel feature development and cherry-pick results.

77|9|Updated Oct 10, 2025

Search Tags:#workspaces #branch-management #git-worktrees #task-orchestration #parallel-development #code-collaboration

Ready to run

npx skills add https://github.com/henkisdabro/wookstar-claude-plugins --skill git-worktrees-henkisdabro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-worktrees
Source: https://github.com/henkisdabro/wookstar-claude-plugins/tree/main/plugins/git-worktrees/skills/git-worktrees
Command: npx skills add https://github.com/henkisdabro/wookstar-claude-plugins --skill git-worktrees-henkisdabro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables engineers to perform parallel feature development by creating isolated Git worktree directories and running the same plan across multiple workspaces, reducing iteration time.

Core Features & Use Cases

Create and manage multiple isolated worktrees for concurrent feature development.
Launch per-worktree agents to execute a shared plan, produce per-worktree RESULTS.md summaries, and compare outcomes.
Cherry-pick the winning changes into the main branch to finalize the best implementation.

Quick Start

Prepare N worktrees and run parallel agents.

Create the parent directory: mkdir -p trees
Create worktrees for each feature: git worktree add -b feature-A ./trees/feature-A origin/feature-A git worktree add -b feature-B ./trees/feature-B origin/feature-B
Launch per-worktree agents to execute the plan and produce RESULTS.md in each workspace using the Task tool: Use the Task tool to start an agent for each worktree with a plan to implement the feature and save a RESULTS.md file in that workspace.
Review RESULTS.md files and cherry-pick the winner into main: git checkout main git cherry-pick feature-B

Frequently Asked Questions about git-worktrees

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

FAQPage Schema

How do I use git worktrees for parallel feature development?▼

Git worktrees allow parallel feature development by creating isolated directory branches. You create separate worktree folders, launch concurrent agents to execute a shared plan in each, and cherry-pick the best changes into main.

What is the best way to run the same plan across multiple git branches concurrently?▼

Running the same plan across multiple branches concurrently involves spawning per-worktree agents using a Task tool. Each agent executes the plan in its isolated workspace and generates a RESULTS.md summary for comparison.

How do I compare feature branches and merge the winning implementation?▼

To compare feature branches and merge the winner, review the RESULTS.md files generated in each worktree directory. After identifying the best outcome, switch to main and cherry-pick the changes from the winning branch.

Does git worktree orchestration require any special dependencies?▼

Git worktree orchestration relies on native Git worktree support and a coordinating Task-based agent system. No external dependencies are required, but you need a parent directory to hold the isolated workspaces.

Can I manage multiple isolated workspaces without stashing my current changes?▼

Managing multiple isolated workspaces without stashing changes is exactly what git worktrees facilitate. They create separate directory trees for different branches, allowing you to run parallel agents and compare outcomes simultaneously.