resolving-merge-conflicts

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

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

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 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: 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 conflicting hunk by preserving both intents where possible, and documents trade-offs when intents are incompatible. - Verification and Completion: Runs the project's typecheck, tests, and formatting checks, then stages, commits, and continues the rebase until finished. - Use Case: You are mid-rebase of a 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 side's logic, run the test suite, and complete the rebase. ## 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 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. Read the commit messages and linked PRs for each side before editing, and never invent new behavior during resolution.

How to continue a git rebase after fixing conflicts?

After resolving the conflicting files, stage them with git add and run git rebase --continue. Repeat the resolve-and-continue cycle until all commits are rebased, then run the project's tests to confirm nothing broke.

Should I use git merge or git rebase for integrating branches?

Both are supported by this workflow. Merge preserves branch history with a merge commit, while rebase replays commits for a linear history. The resolution process is similar: inspect conflicts, resolve hunks, run checks, and finish the operation.

What should I check after resolving merge conflicts?

Run the project's automated checks in order: typecheck first, then tests, then formatting. Fix anything the merge broke before staging and committing, since a conflict-free file can still contain semantic errors.

When should I abort a merge instead of resolving it?

This workflow never aborts: it always resolves the conflict in place. If two intents are truly incompatible, pick the one matching the merge's stated goal and note the trade-off rather than abandoning the merge.