merge-reconciler

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

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Chia1104/agent-air --skill merge-reconciler-chia1104
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-reconciler
Source: https://github.com/Chia1104/agent-air/tree/main/skills/hermes/autonomous-ai-agents/merge-reconciler
Command: npx skills add https://github.com/Chia1104/agent-air --skill merge-reconciler-chia1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When two AI agents working in parallel produce conflicting git branches, neither agent can fairly resolve the conflict — each lacks the peer's context and is biased toward its own changes, leading to overwritten work or abandoned features. This Skill provides an impartial reconciliation procedure that merges both sides based on their stated intents. ## Core Features & Use Cases - Hunk Classification: Categorizes every conflicted hunk as disjoint-intent, same-question-different-answer, or superseded, with per-hunk rationale. - Impartiality Contract: Enforces rules against self-favoring, drive-by edits, and splitting the difference on design decisions. - Kanban Integration: Supports spawning a neutral reconciler agent via delegate_task or a third-profile kanban card with both conflicted cards linked as parents. - Use Case: During a parallel-PR wave, two agent branches collide on a shared module. Spawn a reconciler subagent with both branch names and intent summaries; it classifies each hunk, merges disjoint changes, picks one answer per design collision, runs the build, and hands back a summary listing every decision for human veto. ## Quick Start Resolve the halted merge in this repository between branch-a and branch-b as a neutral reconciler, using both sides' kanban completion summaries as intent sources.

Frequently Asked Questions about merge-reconciler

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

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

Spawn a neutral reconciler agent with the repo path, both branch names, and both sides' intent summaries. It classifies each conflicted hunk as disjoint-intent, same-question-different-answer, or superseded, then merges accordingly and verifies with the project's build and tests.

How to arbitrate conflicting branches in a multi-agent kanban pipeline?▼

Create a reconciliation kanban card assigned to a third profile with both conflicted cards linked as parents. The parent links carry both completion summaries into the reconciler's context, and the card body names the repo path and the two branches.

When should I not use a merge reconciliation skill?▼

Do not use it for conflicts within a single agent's own work, since that agent has full context to resolve them itself. Also skip it for trivial lockfile or generated-file conflicts, which should simply be regenerated instead.

What happens if both sides' intents cannot be recovered?▼

If neither kanban summaries, PR bodies, nor commit messages reveal each side's intent, the reconciler escalates by blocking the kanban card or reporting back rather than guessing. Commit messages alone are considered a thin intent source.

Why does the reconciler avoid splitting the difference on design conflicts?▼

Splitting the difference produces a hybrid neither side designed or asked for. The reconciler picks one answer based on the stated intents and surfaces that design decision explicitly in the hand-back summary so a human can veto it.