resolving-merge-conflicts

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt git workflows and are often resolved hastily, losing the intent behind one side of the change. This Skill provides a disciplined procedure for understanding each conflict, resolving every hunk correctly, and completing the merge or rebase safely. ## Core Features & Use Cases - Conflict Investigation: Inspects the current merge/rebase state, git history, commit messages, PRs, and original tickets 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 they are incompatible—never aborting the merge. - Verification and Completion: Runs the project's automated checks (typecheck, tests, formatting), fixes regressions, then stages, commits, and continues the rebase until finished. - Use Case: You run git rebase main and hit conflicts across three files. The Skill traces each conflicting change back to its originating PR, resolves the hunks without dropping either feature's behavior, runs the test suite, and completes 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?

Examine the conflicting files and git history to understand why each side changed, then resolve each hunk preserving both intents where possible. After resolving, run the project's typecheck, tests, and formatter before staging and committing.

How to continue a git rebase after fixing conflicts?

After resolving the conflicting hunks in each file, stage the resolved files and continue the rebase process. Repeat this for every conflicting commit until all commits are rebased onto the target branch.

Should I use git merge or git rebase when conflicts appear?

Both can produce conflicts; the resolution approach is the same—understand each change's intent and resolve hunks accordingly. The Skill handles either case and finishes whichever operation is in progress rather than aborting it.

Why is aborting a merge conflict resolution discouraged?

Aborting discards progress and leaves the underlying divergence unresolved, so the conflict returns on the next attempt. Resolving each hunk directly, guided by commit messages and original tickets, produces a durable resolution.

What should I check after resolving merge conflicts?

Run the project's automated checks—typically typecheck first, then tests, then formatting—and fix anything the merge broke. Only stage and commit once all checks pass.