| name | multi-agent-vcs |
| description | This skill should be used when dispatching subagents for parallel development, coordinating multi-branch implementations, or when "parallel agents", "orchestrator commits", "subagent filesystem only", "multi-agent git", or "prevent stack corruption" are mentioned. Prevents stack corruption through orchestrator-only git policy. |
| metadata | {"version":"1.0.0","author":"outfitter","category":"version-control"} |
Multi-Agent Version Control
Tool-agnostic patterns for coordinating git operations across parallel AI agents.
<when_to_use>
- Dispatching subagents for parallel work
- Planning multi-branch implementations
- Recovering from parallel agent corruption
- Any workflow where multiple agents touch the filesystem
</when_to_use>
The Problem
When parallel subagents perform git operations independently:
- Mixed content - Multiple features end up in wrong branches
- Broken stacks - Branches become siblings instead of parent-child
- Mislabeled PRs - PR titles don't match branch content
- Hours of recovery - Manual intervention required to fix structure
This happens because each agent sees the same starting state and creates branches independently, resulting in siblings instead of a proper stack.
The Policy
Subagents MUST NOT perform git operations.
Only the orchestrator handles git state. Subagents write code to the filesystem and report completion.
ALWAYS:
