resolving-merge-conflicts

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

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

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's changes or breaking the build. This Skill provides a disciplined process for understanding each conflict's origin and resolving it correctly. ## Core Features & Use Cases - Intent Analysis: Traces each conflicting change back to its commit messages, PRs, and original issues to understand why both sides changed the code. - Hunk-by-Hunk Resolution: Resolves each conflict hunk by preserving both intents where possible, or choosing the side matching the merge's stated goal while documenting trade-offs. - Verification and Completion: Runs the project's automated checks (typecheck, tests, format) after resolving, then stages, commits, and continues the rebase to completion. - Use Case: You are mid-rebase of a long-lived feature branch onto main and hit conflicts in five files. Use this Skill to investigate each conflict's origin, resolve them without losing either side's logic, run the test suite, and finish the rebase. ## Quick Start Resolve the current in-progress git merge conflict in my repository, preserving the intent of both branches, then run the tests 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?

Resolving a git merge conflict means inspecting the conflicting files, understanding why each side changed the code, and editing each conflicted hunk to preserve both intents where possible. After resolving, stage the files, run the project's tests, and commit to complete the merge.

How to resolve conflicts during a git rebase?

During a rebase, resolve each conflicted file as it appears, stage the changes, and run git rebase --continue to proceed through remaining commits. Repeat until all commits are rebased, and run the project's checks to confirm nothing broke.

Should I abort a merge when conflicts are too complex?

This Skill's approach is to always resolve rather than abort. Investigate the commit messages, PRs, and original issues behind each change so you can resolve hunks deliberately instead of abandoning the merge.

What should I do after resolving merge conflicts?

After resolving, run the project's automated checks, typically typecheck, then tests, then formatting, and fix anything the merge broke. Then stage everything and commit, or continue the rebase until it finishes.

How do I choose which side of a conflict to keep?

Prefer preserving both intents when the changes are compatible. When they conflict fundamentally, pick the side matching the merge's stated goal, note the trade-off, and never invent new behavior that neither side intended.