resolving-merge-conflicts

Resolves in-progress git merge and rebase conflicts by analyzing commit history and intent.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill resolving-merge-conflicts-fatih0234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/engineering/resolving-merge-conflicts
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill resolving-merge-conflicts-fatih0234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are often resolved hastily, losing the intent behind one side of the change. This Skill provides a disciplined workflow for understanding both sides of every conflict and resolving them without losing work. ## Core Features & Use Cases - State Inspection: Examines the current merge/rebase state, git history, and all conflicting files before touching anything. - Intent Analysis: Traces each conflict back to its primary sources—commit messages, PRs, and original issues—to understand why each change was made. - Hunk-by-Hunk Resolution: Preserves both intents where possible, picks the side matching the merge's stated goal when incompatible, and never aborts or invents new behavior. - Verification & Completion: Runs the project's automated checks (typecheck, tests, format), fixes breakage, then stages, commits, and finishes the merge or rebase. - Use Case: You are mid-rebase of a long-lived feature branch onto main and hit conflicts across five files. The Skill walks through each conflict, checks the original PRs, resolves each hunk, runs the test suite, and completes the rebase. ## Quick Start Resolve the current in-progress git merge conflict in this repository, preserving the intent of both branches, then run the project checks and finish the merge.

Frequently Asked Questions about resolving-merge-conflicts

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

FAQPage Schema
How do I resolve a git merge conflict without losing changes?▼

Inspect the current merge state and conflicting files first, then trace each change back to its commit messages, PRs, and original issues to understand intent. Resolve each hunk preserving both intents where possible, run the project's checks, then stage and commit.

How to finish a git rebase after resolving conflicts?▼

After resolving each conflicting hunk, stage the files and continue the rebase until all commits are replayed. Run the project's automated checks such as typecheck and tests before finishing to catch anything the rebase broke.

Should I use git merge or git rebase when conflicts happen?▼

The resolution workflow is the same for both: understand each side's intent, resolve hunks, verify with automated checks, and complete the operation. The Skill handles whichever operation is already in progress rather than choosing between them.

When should I abort a merge instead of resolving conflicts?▼

This workflow never aborts; it always resolves. When two changes are truly incompatible, it picks the side matching the merge's stated goal and notes the trade-off rather than inventing new behavior or abandoning the merge.

Why do merge conflicts keep breaking my tests after resolution?▼

Conflicts resolved syntactically can still break semantics when two changes interact. Running the project's full check suite—typecheck, then tests, then format—after resolution catches these breakages before the merge is committed.