resolving-merge-conflicts

Resolves in-progress git merge and rebase conflicts while preserving both change intents.

Updated Sep 21, 2026
One-click install
npx skills add https://github.com/maxentr/la-cuisine-de-mm --skill resolving-merge-conflicts-maxentr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/maxentr/la-cuisine-de-mm/tree/main/.agents/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/maxentr/la-cuisine-de-mm --skill resolving-merge-conflicts-maxentr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are often resolved hastily, losing the intent of one side's changes or breaking the build. This Skill provides a disciplined workflow for understanding each conflict's origin, resolving hunks correctly, and finishing the merge safely. ## Core Features & Use Cases - Conflict Investigation: Inspects the current merge/rebase state, git history, commit messages, PRs, and original issues to understand why each change was made. - Intent-Preserving Resolution: Resolves each conflicting hunk by preserving both intents where possible, choosing the side matching the merge's stated goal when they are incompatible, and never inventing new behavior or aborting. - Verification and Completion: Runs the project's automated checks (typecheck, tests, format), fixes anything the merge broke, then stages, commits, and continues the rebase to completion. - Use Case: During a long-running feature branch rebase onto main with conflicts across several files, use this Skill to trace each conflict back to its originating PR, resolve hunks without losing either side's logic, and verify the result with the project's test suite. ## Quick Start Resolve the current in-progress git merge conflict in my repository and finish the merge after running the project's checks.

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 step by step?

First inspect the current merge state and conflicting files, then trace each conflict to its source commits and PRs to understand intent. Resolve each hunk preserving both intents where possible, run the project's checks, then stage and commit.

How to resolve conflicts during a git rebase?

During a rebase, resolve each conflicting hunk as it appears, stage the resolved files, and continue the rebase until all commits are replayed. Investigate commit messages and original issues to understand why each change was made before choosing a resolution.

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

Both can produce conflicts, and the resolution approach is the same: understand each side's intent and preserve both where possible. The Skill supports in-progress states of either operation and finishes whichever one is underway.

What should I do after resolving merge conflicts?

After resolving, run the project's automated checks such as typecheck, tests, and formatting, and fix anything the merge broke. Then stage all changes, commit, and continue the rebase if one is in progress.

When should I abort a merge instead of resolving it?

This workflow never aborts; it always resolves the conflict in place. If two changes are truly incompatible, pick the side matching the merge's stated goal and note the trade-off rather than inventing new behavior.