resolving-merge-conflicts

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

2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill resolving-merge-conflicts-moofonli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/MoofonLi/dev-ready/tree/main/.agents/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill resolving-merge-conflicts-moofonli

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 procedure for understanding each conflict's origin and resolving it correctly. ## Core Features & Use Cases - Intent-Preserving Resolution: Traces each conflicting change back to its commit messages, PRs, and original issues so both intents are preserved where possible. - Guided Hunk-by-Hunk Workflow: Resolves each conflict hunk against the merge's stated goal, never aborting and never inventing new behavior. - Post-Resolution Verification: Discovers and runs the project's automated checks (typecheck, tests, format) before staging, committing, and completing the merge or rebase. - Use Case: During a long-running feature branch rebase onto main, conflicts appear across several files. The Skill inspects the history behind each change, resolves every hunk, runs the test suite, and continues the rebase to completion. ## 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 a git merge conflict without losing changes?

Resolve each conflict hunk by first understanding why both changes were made, using commit messages, PRs, and original tickets. Preserve both intents where possible, and where they are incompatible, follow the merge's stated goal and note the trade-off.

How to continue a git rebase after fixing conflicts?

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

Should I ever use git merge --abort when resolving conflicts?

This workflow never aborts; it always resolves the conflict in place. Aborting discards progress, so instead each hunk is resolved deliberately based on the original intent of both sides.

What checks should run after resolving merge conflicts?

Run the project's existing automated checks, typically typecheck first, then tests, then formatting. Fix anything the merge broke before staging and committing the resolution.

When is manual conflict resolution better than accepting one side?

Manual resolution is better when both sides contain meaningful changes that must coexist. Blindly accepting ours or theirs discards intent, while hunk-by-hunk analysis preserves both behaviors where compatible.