resolving-merge-conflicts

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

10|3|Updated Jul 18, 2019
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill resolving-merge-conflicts-tanqimin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill resolving-merge-conflicts-tanqimin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are risky to resolve by hand, since blindly picking one side can silently discard a teammate's intended change. This Skill guides a structured resolution process that preserves the intent of both sides and finishes the merge safely. ## Core Features & Use Cases - State Inspection: Examines the current merge/rebase state, git history, and conflicting files before touching anything. - Intent Analysis: Traces each conflict back to its primary sources—commit messages, PRs, and original issues—to understand why each change was made. - Hunk-by-Hunk Resolution: Resolves each conflict hunk while preserving both intents where possible, never aborting and never inventing new behavior. - Verification & Completion: Runs the project's automated checks (typecheck, tests, format), fixes merge breakage, then stages, commits, and continues the rebase to completion. - Use Case: You run git rebase main on a long-lived feature branch and hit conflicts across five files. The Skill inspects each conflict, reads the relevant commits and PRs, resolves every hunk in line with the rebase goal, 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 safely?

Start by inspecting the current merge state and conflicting files, then trace each change to its commit messages and PRs to understand intent. Resolve each hunk preserving both intents where possible, run the project's tests, then stage and commit.

How to resolve conflicts during a git rebase?

During a rebase, resolve each conflicted hunk as it appears, stage the resolved files, and continue the rebase until all commits are replayed. Never abort midway; always resolve and verify with the project's automated checks.

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

Both can produce conflicts, and the resolution approach is the same: understand each side's intent and resolve hunk by hunk. Choose based on your team's history preference—merge preserves branch structure, rebase creates a linear history.

When should I abort a merge instead of resolving conflicts?

This Skill's policy is to always resolve and never abort, since aborting discards progress and leaves the underlying divergence unaddressed. If intents are incompatible, pick the side matching the merge's stated goal and document the trade-off.

Why do merge conflicts keep breaking my tests after resolution?

Conflicts resolved textually can still break semantics when two changes interact, such as a renamed function used by the other branch. Always run the project's typecheck, tests, and formatter after resolving, and fix any breakage before committing.