fork-join

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.

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.

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.

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.

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.