resolving-merge-conflicts

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt git workflows and are often resolved hastily, losing the intent of one side or introducing broken code. This Skill provides a disciplined process for understanding each conflict and resolving it correctly. ## Core Features & Use Cases - Conflict Analysis: Inspect the current merge/rebase state, git history, and conflicting files before touching anything. - Intent-Preserving Resolution: Trace each change back to commit messages, PRs, and original issues so both intents are preserved where possible, with trade-offs noted when they are incompatible. - Verification and Completion: Run the project's automated checks (typecheck, tests, format), fix merge breakage, then stage, commit, and continue the rebase to completion. - Use Case: During a long-running feature branch rebase onto main, conflicts appear in five files. Use this Skill to understand why each side changed the code, resolve every hunk without inventing new behavior, and finish the rebase with all checks passing. ## Quick Start Resolve the current git merge conflict in this repository, preserving the intent of both branches and running the project checks before committing.

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 git merge conflicts without losing changes?▼

Resolve git merge conflicts by first inspecting the merge state and history, then tracing each conflicting change to its commit message, PR, or issue to understand intent. Preserve both intents where possible, and run the project's checks before committing.

How to continue a git rebase after fixing conflicts?▼

After resolving each conflicting hunk, stage the fixed files and continue the rebase process until all commits are rebased. Run typecheck, tests, and formatting first to confirm the resolution did not break anything.

Should I ever use git merge --abort during conflict resolution?▼

This workflow never aborts; it always resolves the conflict in place. Aborting discards progress, so instead each hunk is resolved by matching the merge's stated goal and noting any trade-offs.

What should I check before committing a merge conflict resolution?▼

Before committing, discover and run the project's automated checks, usually typecheck first, then tests, then formatting. Fix anything the merge broke, then stage everything and commit or continue the rebase.

When is manual conflict resolution better than accepting one side?▼

Manual resolution is better when both sides contain meaningful changes, such as parallel feature work on the same code. Blindly accepting one side discards intent, while analyzing commit messages and PRs lets you preserve both behaviors where compatible.