resolving-merge-conflicts

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

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill resolving-merge-conflicts-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/2026-09-10/resolving-merge-conflicts
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill resolving-merge-conflicts-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are often resolved hastily, losing the intent behind one side of the change or introducing regressions. This Skill provides a disciplined workflow for understanding each conflict, resolving every hunk correctly, and finishing the merge safely. ## Core Features & Use Cases - State Inspection: Examines the current merge/rebase state, git history, and conflicting files before touching anything. - Intent-Driven Resolution: Traces each conflict back to its primary sources (commit messages, PRs, original issues) so resolutions preserve both intents where possible, and never invents new behavior or aborts the merge. - Verification and Completion: Runs the project's automated checks (typecheck, tests, format), fixes merge-induced breakage, then stages, commits, and continues the rebase to completion. - Use Case: You are mid-rebase of a feature branch onto main and hit conflicts in three files. The Skill walks through each hunk, checks the original PRs to understand both sides, resolves them, runs the test suite, and finishes the rebase. ## Quick Start Resolve the current git merge conflict in this repository, preserving the intent of both branches, then run the project checks and complete 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 hunk by first understanding why both changes were made, using commit messages, PRs, and original issues as sources. Preserve both intents where possible, and where they conflict, pick the side matching the merge's stated goal while noting the trade-off.

How to finish a git rebase after fixing conflicts?

After resolving all conflicting hunks, stage the resolved files and continue the rebase until every commit is replayed. Run the project's automated checks such as typecheck and tests before completing to catch anything the merge broke.

Should I ever use git merge --abort when resolving conflicts?

This workflow never aborts; it always resolves the conflict in place. Aborting discards progress and context, so instead each hunk is resolved deliberately based on the original intent of both changes.

What checks should I run after resolving merge conflicts?

Discover the project's existing automated checks and run them in order: typically typecheck first, then tests, then formatting. Fix anything the merge broke before staging and committing the resolution.

When is manual conflict resolution not appropriate?

Manual resolution is not appropriate when you do not understand the intent behind either side of the conflict. In that case, first investigate the commit history, pull requests, and original tickets before editing any hunk.