- Home
- Skills
- Agents & Orchestration
- Agent Branch Coordinator for Parallel Coding Agents
Works with the AI Agents you already use
Agent Branch Coordinator for Parallel Coding Agents
**The problem.** Running three agents at once is easy.
$12
Agent Branch Coordinator for Parallel Coding Agents
Example session with this skill installed
I have three agents working on our TypeScript/Python repo on branches agent/claude-code/rename-fmt, agent/cursor/report-export and agent/cline/user-schema. Can you check whether they're safe to merge and tell me in what order?
- Read your context and instructions
- Compiled the agent branch coordinator
Example session (illustrative).
1. Preconditions checked
harness0.1.0 is on PATH,harness.tomlis committed onmainwith[conflicts] branches = ["agent/*"].- Ran
git fetchand compared againstorigin/mainso a stale local main can't shift merge bases.
2. Detector run (harness conflicts --base origin/main --json, from the main checkout)
harness conflicts · agent/claude-code/rename-fmt · agent/cline/user-schema · agent/cursor/report-export
L1 renamed-symbol `fmt` [agent/claude-code/rename-fmt -> agent/cursor/report-export]
`agent/claude-code/rename-fmt` renames `fmt` to `format_value`, and `agent/cursor/report-export` adds references to the old name (app/report.py)
fix: rename references `fmt` -> `format_value` in app/report.py (harness conflicts --fix)
L2 removed-member `User.email` [agent/cline/user-schema -> agent/cursor/report-export]
`agent/cline/user-schema` removes `email` from `User`, and `agent/cursor/report-export` adds code reading `email` (web/export.ts): schema drift that no textual merge conflict will reveal
BLOCKED: 1 conflict(s) need a human
Exit code 1. git merge would report no textual conflicts for any of these pairs.
3. Level 1 fix applied in the report-export worktree (the branch referencing the old name):
harness conflicts --fix agent/claude-code/rename-fmt agent/cursor/report-exportprintedfixed app/report.py: `fmt` -> `format_value`.git diffshowed rename-only edits;git grep -nw fmtfound only the old definition inapp/lib.py, whichrename-fmtreplaces. Committed as a rename-only commit on that branch, with your approval. The fullharness rungate for this branch waits untilrename-fmtis merged, becausereport-exportnow importsformat_value, which only exists after that merge.
4. Level 2 conflict: needs your decision
user-schema renames User.email to User.emailAddress; report-export adds a CSV column that reads u.email. Proposal: merge report-export first, then user-schema rebases and migrates the new u.email read in web/export.ts, because whoever makes the breaking change owns the migration.
5. Proposed merge order
agent/claude-code/rename-fmt: the rename; its consumer is already fixed.agent/cursor/report-export: rebase on main, rerunharness run, merge.agent/cline/user-schema: rebase, updateweb/export.ts,harness run, merge.
After each merge I rerunharness conflicts. Nothing has been merged yet; say go and I'll start with step 1.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem. Running three agents at once is easy. Merging their work is where it goes wrong. Agent A renames a function or drops a field, agent B adds new code that uses the old name, git merges both without complaint, and main stops building. Textual merge conflicts never show this kind of semantic conflict.
What the agent does with this skill.
- Sets up the parallel layout: a committed
harness.tomlwith[conflicts] branches = ["agent/*"], oneagent/<agent-id>/<task>branch and one git worktree per agent, all branched from the same up-to-date base. - Runs
harness conflictsat the right points (mid-task checkpoints, before merging, after every merge) and knows what it compares: local branches matching the glob, the checked-out branch from its working tree, every other branch from its last commit. - Reads each finding (
renamed-symbol,lockfile,removed-symbol,removed-member,signature-change,concurrent-edit) and knows which ones are Level 1 (auto-fixable) and which are Level 2 (need a human). - Applies
harness conflicts --fixfrom the right worktree, then checks what the codemod left alone (TypeScript/JavaScript property accesses and shorthand properties, files that declare the old name themselves) and reviews Python edits, where attribute accesses and keyword arguments with the old name are renamed too. - Produces an ordered merge plan with a reason for each step. The rules: whoever makes a breaking change owns the migration, renames merge after the fix is applied, and every merge is followed by a rebase and a fresh check.
- States the tool's blind spots honestly: structural rules cover TypeScript, JavaScript and Python only, only newly added references are detected, and stale squash-merged branches cause false positives.
Who it's for. Developers and teams running Claude Code, Cursor, Codex CLI, Cline or similar agents in parallel on the same repository who want a repeatable way to merge their branches.
Requirements. A git repository; the AgentHarness harness binary (free, open source: prebuilt releases or cargo install --locked --git https://github.com/KadonWills/agent-harness harness-cli. The harness-cli crate on crates.io is a different tool); Docker if you also run the full harness run gate. Structural conflict detection covers TypeScript/TSX, JavaScript/JSX and Python.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Structural rules apply only to TypeScript, JavaScript, and Python. Rust and Go support is limited to lockfiles. Agents must commit work for sibling detection to see their changes.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 17 days ago
- Software
Githarness (AgentHarness CLI)
Docker (for the full `harness run` gate)