resolving-merge-conflicts

Resolves in-progress git merge and rebase conflicts by analyzing commit history and intent.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill resolving-merge-conflicts-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill resolving-merge-conflicts-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development workflows and are often resolved hastily, losing the intent behind one side of the change. This Skill provides a disciplined process for understanding both sides of every conflict and resolving them correctly. ## Core Features & Use Cases - State Inspection: Examines the current merge/rebase state, git history, and all conflicting files before touching anything. - Intent Analysis: Traces each conflict back to its primary sources—commit messages, pull requests, and original issues—to understand why each change was made. - Intent-Preserving Resolution: Resolves each hunk by preserving both intents where possible, never inventing new behavior and never aborting the merge. - Verification & Completion: Runs the project's automated checks (typecheck, tests, format), fixes regressions, then stages, commits, and finishes the merge or rebase. - Use Case: You run git rebase main on a long-lived feature branch and hit conflicts across five files. The Skill walks through each conflict, reads the original PRs to understand both changes, resolves the hunks, 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 tests 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—read the commit messages, PRs, and original issues. Preserve both intents where possible, and where they are incompatible, pick the one matching the merge's stated goal and note the trade-off.

How to finish a git rebase after resolving conflicts?

After resolving each conflicted file, stage the changes and continue the rebase until all commits are replayed. Run the project's automated checks such as typecheck and tests before finishing to catch anything the merge broke.

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

Both produce conflicts when branches diverge, and the resolution process is the same: inspect the state, understand each change's intent, and resolve hunks without inventing new behavior. The choice depends on your team's history preferences, not conflict handling.

Why is git merge --abort discouraged during conflict resolution?

Aborting discards progress and leaves the underlying divergence unresolved, so the conflict will reappear on the next attempt. Always resolve conflicts forward by understanding both sides and completing the merge or rebase.

What should I check after resolving merge conflicts?

Run the project's automated checks, typically typecheck first, then tests, then formatting. Fix anything the merge broke before staging everything and committing to finish the merge or rebase.