resolving-merge-conflicts

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development work and are often resolved hastily, losing the intent of one side's changes or introducing broken code. This Skill provides a disciplined workflow for understanding each conflict's origin, resolving hunks correctly, and verifying the result with the project's automated checks. ## Core Features & Use Cases - Conflict Investigation: Inspect the current merge/rebase state, git history, commit messages, PRs, and original issues to understand why each change was made. - Intent-Preserving Resolution: Resolve 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. - Verification and Completion: Run the project's typecheck, tests, and formatting checks, fix anything the merge broke, then stage, commit, and continue the rebase to completion. - Use Case: You are rebasing a long-lived feature branch onto main and hit conflicts in three files. Use this Skill to trace each conflict back to its originating PR, resolve the hunks without losing either change, run the test suite, and finish the rebase cleanly. ## Quick Start Resolve the current git merge conflict in my repository, verify the project checks pass, 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?▼

Start by inspecting the current merge state and the conflicting files, then trace each conflict to its source commits, PRs, or issues 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 the same way as a merge: understand both changes' intent, pick the resolution matching the rebase goal, and stage the files. Then continue the rebase until all commits are replayed, never aborting midway.

Should I use git merge or git rebase for my branch?▼

This Skill handles conflicts for both operations identically, since the resolution principles are the same. The choice depends on your team's workflow: merge preserves branch history, while rebase creates a linear commit history.

What should I do after resolving merge conflicts?▼

After resolving, run the project's automated checks in order: typecheck, then tests, then formatting. Fix anything the merge broke, stage all resolved files, and commit to finish the merge or continue the rebase.

When should I abort a merge instead of resolving conflicts?▼

This Skill's guidance is to always resolve and never abort, since conflicts indicate real overlapping work that must be reconciled. Aborting only postpones the problem; the correct approach is understanding each change's intent and resolving deliberately.