resolving-merge-conflicts

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

Updated May 31, 2026
One-click install
npx skills add https://github.com/AlexanderNarbaev/agi --skill resolving-merge-conflicts-alexandernarbaev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/matt-pocock/resolving-merge-conflicts
Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill resolving-merge-conflicts-alexandernarbaev

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. This Skill provides a disciplined workflow for understanding each conflict's origin, resolving every hunk 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 completes the merge or continues the rebase to the end. - Use Case: You run git rebase main on a long-lived feature branch and hit conflicts across five files. The Skill traces each conflict back to its originating commits, resolves them without inventing new behavior, runs the test suite, and finishes the rebase. ## Quick Start Resolve the current git merge conflict in my repository, 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 step by step?

First inspect the current merge state and conflicting files, then trace each conflict to its source commits, PRs, or issues. Resolve each hunk preserving both intents where possible, run the project's checks, then stage everything and commit.

How to finish a git rebase after fixing conflicts?

After resolving each conflicting hunk, stage the files and continue the rebase until all commits are replayed. The Skill repeats this resolve-and-continue loop and runs automated checks before finishing.

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

The Skill supports both in-progress merges and rebases equally. It follows the operation already started in your repository rather than choosing one, resolving conflicts according to the merge's stated goal.

What happens when two conflicting changes are incompatible?

When both intents cannot be preserved, the resolution picks the change matching the merge's stated goal and records the trade-off. It never invents new behavior and never aborts the merge with --abort.

Why run tests after resolving merge conflicts?

Conflict resolution can silently break code even when hunks apply cleanly. Running the project's automated checks—typically typecheck, then tests, then formatting—catches anything the merge broke before committing.