merge-conflict-tool

Automates git merge, rebase, and cherry-pick conflict resolution with verification.

Updated May 3, 2026
One-click install
npx skills add https://github.com/dawsonl1/merge-conflict-tool --skill merge-conflict-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-conflict-tool
Source: https://github.com/dawsonl1/merge-conflict-tool/tree/main/plugins/merge-conflict-tool/skills/merge-conflict-tool
Command: npx skills add https://github.com/dawsonl1/merge-conflict-tool --skill merge-conflict-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill resolves git merge, rebase, or cherry-pick conflicts by preserving both sides' work and using a structured approach to conflict resolution, eliminating the need for manual intervention and reducing merge-related errors.

Core Features & Use Cases

  • Conflict Detection and Clustering: Automatically identifies and clusters related conflicts based on file relationships and shared commit history.
  • Paired Defender Subagents: Independently analyzes both sides of each conflict cluster to preserve intent and avoid bias.
  • Synthesized Resolution: Categorizes conflicts as overlap, complement, or genuine conflict and synthesizes a resolution that preserves both sides' contributions.
  • Verification and Testing: Provides verification through targeted tests, frontend build, and visual verification for UI changes, ensuring accuracy before continuing the merge.

Quick Start

Activate the merge-conflict-tool skill when you encounter a git merge conflict and let it handle the resolution.

Frequently Asked Questions about merge-conflict-tool

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

FAQPage Schema
How do I resolve git merge conflicts automatically without losing changes from either branch?

Automated git merge conflict resolution analyzes both sides of conflicts using paired defender subagents. It categorizes conflicts as overlap, complement, or genuine conflict, then synthesizes a resolution that preserves both sides' contributions.

Can I use an automated tool to resolve rebase or cherry-pick conflicts in git?

Yes, automated conflict resolution supports git rebase and cherry-pick operations. It identifies and clusters related conflicts based on file relationships and shared commit history, resolving them systematically without manual intervention.

How does conflict resolution verification work before continuing a git merge?

Verification involves running targeted tests, frontend builds, and visual verification for UI changes. This ensures the synthesized conflict resolution is accurate and does not break existing functionality before the git merge continues.

What do I need to run an automated git conflict resolution tool?

You need git and Python installed, along with specific library dependencies for execution and verification. The environment must support running scripts to analyze conflicts and execute verification processes.

What is the best way to handle complex git merge conflicts in code collaboration workflows?

The best approach uses paired defender subagents to independently analyze both sides of each conflict cluster, avoiding bias and preserving intent. This structured method eliminates manual intervention and reduces merge-related errors in code collaboration.

Why does automated conflict resolution categorize conflicts as overlap, complement, or genuine conflict?

Categorizing conflicts as overlap, complement, or genuine conflict helps the resolution tool determine how to synthesize a resolution that preserves both sides' contributions accurately, ensuring no work is lost during the git merge process.