fork-join

Orchestrate parallel git worktrees with subagents and sequential merges.

70|42|Updated Mar 27, 2026

Search Tags:#automation #git #workflow #worktree #refactor #parallelism

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill fork-join

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fork-join
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/fork-join
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill fork-join

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running batches of independent work in a single branch risks conflicts, missed coordination, and duplicated effort, so this Skill orchestrates the decomposition, verification, and merging of parallel git worktrees without burdening you with manual branching.

Core Features & Use Cases

Independent work unit identification: Analyze the task details and CLAUDE.md context to split the job into nonconflicting units before any work begins.
Parallel subagent management: Fork worktrees, launch AI subagents with precise scope instructions, and ensure each worktree stays clean with committed changes.
Sequential merging with safeguards: Validate each fork through the provided hooks, handle status checks, and merge branches back into the base sequentially to avoid corruption.

Quick Start

Issue the /fork-join command with a batch of independent refactors so the coordinator can create worktrees, launch subagents, and merge results for you.

Frequently Asked Questions about fork-join

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

FAQPage Schema

How do I run parallel git worktrees for batch refactors without causing branch conflicts?▼

Running parallel git worktrees for batch refactors without conflicts requires decomposing independent tasks into isolated branches, launching dedicated subagents per worktree, and sequentially merging verified commits back to avoid corruption.

What is git worktree orchestration and when do I need it for concurrent migrations?▼

Git worktree orchestration coordinates decomposition, parallel execution, and sequential merging of isolated branches. You need it for concurrent migrations touching disjoint files, ensuring each worktree runs a dedicated subagent and verifies clean commits before merging.

Can I use parallel worktrees to generate independent components simultaneously?▼

Yes, you can use parallel worktrees to generate independent components simultaneously by forking isolated git branches for each component. A dedicated subagent handles each worktree with precise scope instructions to keep changes disjoint before sequential merging.

Does fork-join work with existing git workflows and CLAUDE.md project context?▼

Yes, fork-join integrates with existing git workflows by analyzing CLAUDE.md context to split jobs into nonconflicting work units. It creates worktrees, launches scoped subagents, validates status through hooks, and sequentially merges branches back to your base.

What are the limitations of using parallel git worktrees for automated refactoring?▼

Parallel git worktrees for automated refactoring are limited to tasks touching disjoint files without shared dependencies. Work units with overlapping file modifications risk conflicts during sequential merging, making this approach unsuitable for tightly coupled changes.