resolving-merge-conflicts

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/mikalv/pi-extensions --skill resolving-merge-conflicts-mikalv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/mikalv/pi-extensions/tree/main/packages/pi-atelier/.agents/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/mikalv/pi-extensions --skill resolving-merge-conflicts-mikalv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development flow and are often resolved hastily, losing the intent behind one side of the changes. 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 git history, commit messages, PRs, and original issues to understand why each conflicting change was made. - Intent-Preserving Resolution: Resolves each hunk by preserving both intents where possible, and documents trade-offs when they are incompatible. - Verification and Completion: Runs the project's automated checks (typecheck, tests, format) and finishes the merge or continues the rebase to completion. - Use Case: You are mid-rebase of a long-lived feature branch and hit conflicts across several files. Use this Skill to trace each conflict back to its source commits, resolve them without losing either side's behavior, run the test suite, and complete the rebase. ## Quick Start Resolve the current in-progress git merge conflict in this 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 a git merge conflict without losing changes?▼

Resolve each conflicting hunk by first understanding why both changes were made, then preserving both intents where possible. Check commit messages, PRs, and original issues to understand intent before editing, and never invent new behavior during resolution.

How to continue a git rebase after fixing conflicts?▼

After resolving the conflicted files, stage everything and continue the rebase process until all commits are rebased. Repeat the resolve-and-continue cycle for each conflicting commit rather than aborting the rebase.

Should I run tests after resolving merge conflicts?▼

Yes, always run the project's automated checks after resolving conflicts, typically typecheck first, then tests, then formatting. Merges can silently break behavior even when conflicts resolve cleanly, so fix anything the merge broke before committing.

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

This workflow never aborts: it always resolves the conflict and finishes the merge or rebase. When two changes are truly incompatible, pick the one matching the merge's stated goal and note the trade-off in the commit.

Why do merge conflicts happen during a rebase?▼

Conflicts occur when the same lines were changed differently on both branches being integrated. During a rebase this can repeat across multiple commits, so each conflicting commit must be resolved and continued individually.