agent-merge-conflict-arbiter

Resolve git merge conflicts between two agent branches as a neutral third party.

239k|48.8k|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/NousResearch/hermes-agent --skill agent-merge-conflict-arbiter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-merge-conflict-arbiter
Source: https://github.com/NousResearch/hermes-agent/tree/main/optional-skills/autonomous-ai-agents/agent-merge-conflict-arbiter
Command: npx skills add https://github.com/NousResearch/hermes-agent --skill agent-merge-conflict-arbiter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When two AI agents work in parallel on the same repository, their branches inevitably collide. Each agent lacks the peer's context and tends to either overwrite the peer's work or abandon its own changes. This Skill provides an impartial reconciler that reads both diffs and both sides' stated intents, then produces a merged result without favoring either party.

Core Features & Use Cases

  • Hunk Classification: Categorizes every conflict marker as disjoint-intent, same-question-different-answer, or superseded, then applies the correct resolution rule.
  • Impartiality Contract: Operates as a third-profile spawned agent so the reconciler is structurally unbiased toward either original worker.
  • Intent-Aware Decisions: Pulls completion summaries from kanban cards or PR bodies to judge design questions, never splitting the difference into a hybrid nobody designed.
  • Use Case: Two agents in a parallel-PR wave both modify the same authentication module. Spawn this arbiter with both branch names and both kanban summaries to produce a single merged commit with every design decision explicitly documented.

Quick Start

Spawn a neutral subagent with the repo path, both branch names, and both sides' intent summaries, instructing it to follow the agent-merge-conflict-arbiter skill.

Frequently Asked Questions about agent-merge-conflict-arbiter

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

FAQPage Schema
How do I resolve merge conflicts between two AI agents in git?

Spawn a neutral third-profile agent and load the agent-merge-conflict-arbiter skill. Pass both branch names and both sides' intent summaries (kanban completion notes or PR bodies) so the arbiter can classify each hunk and apply the correct resolution rule.

What is the best way to handle parallel agent branches colliding?

Use a kanban reconciliation card assigned to a third profile with both conflicted cards linked as parents. The parent links carry both sides' completion summaries into the reconciler's context automatically, avoiding self-favoring bias.

Can a merge conflict resolver avoid favoring one side?

Yes, by spawning the resolver as a third profile rather than from either conflicting agent. The impartiality contract requires stating structural bias if it exists and weighing the other side's intent deliberately.

When should I not use an automated merge conflict arbiter?

Do not use it for conflicts within a single agent's own work, or for trivial lockfile and generated-file conflicts. Those should be regenerated rather than reconciled through intent-based arbitration.

Why does splitting the difference on a design conflict fail?

Splitting produces a hybrid that neither side designed and that satisfies neither stated intent. The arbiter picks one answer per stated intent and surfaces the decision in the hand-back summary for human veto.