resolving-merge-conflicts

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

3|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/mambo-wang/CodingHub --skill resolving-merge-conflicts-mambo-wang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/mambo-wang/CodingHub/tree/main/.codebuddy/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/mambo-wang/CodingHub --skill resolving-merge-conflicts-mambo-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are often resolved hastily, losing one side's intent or breaking the build. This Skill provides a disciplined workflow for understanding each conflict's origin, resolving every hunk correctly, and verifying the result with the project's automated checks. ## 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 hunk by preserving both intents where possible, choosing the side matching the merge's stated goal when incompatible, and never aborting or inventing new behavior. - Verification and Completion: Runs the project's typecheck, tests, and formatting checks, 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, conflicts appear across five files. The Skill traces each conflicting change to its original PR, resolves hunks to keep both the new feature logic and upstream refactors, runs the test suite, and finishes the rebase cleanly. ## Quick Start Resolve the current git merge conflict in my 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 git merge conflicts without losing changes?▼

Investigate the primary sources for each conflict first: read commit messages, PRs, and original issues to understand intent. Then resolve each hunk preserving both intents where possible, and run the project's typecheck and tests before committing.

How to finish a git rebase after fixing conflicts?▼

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

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

Both operations can produce conflicts, and the resolution approach is the same: understand each change's intent and resolve hunks accordingly. The Skill supports in-progress states of either operation and never aborts the process.

What should I check before committing a conflict resolution?▼

Run the project's automated checks, typically typecheck first, then tests, then formatting. Fix anything the merge broke, stage everything, and only then commit to finish the merge or continue the rebase.

When should I not resolve a merge conflict automatically?▼

Avoid resolving when you cannot determine the original intent of either side from commit history, PRs, or tickets. The workflow forbids inventing new behavior; incompatible changes should follow the merge's stated goal with the trade-off noted.