resolving-merge-conflicts

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

7|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/J0Jng/MathModelingAgents --skill resolving-merge-conflicts-j0jng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/J0Jng/MathModelingAgents/tree/main/.claude/skills/engineering/resolving-merge-conflicts
Command: npx skills add https://github.com/J0Jng/MathModelingAgents --skill resolving-merge-conflicts-j0jng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are often resolved hastily, losing the intent of one side's changes or breaking the build. This Skill provides a disciplined workflow for understanding each conflict's origin, resolving hunks correctly, and verifying the result with the project's automated checks. ## 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 commit messages, PRs, and original issues so resolutions preserve both intents where possible, and never invents new behavior. - Verification and Completion: Runs the project's typecheck, tests, and formatting after resolution, then stages, commits, and continues the rebase to completion. - Use Case: You are mid-rebase of a long-lived feature branch onto main and hit conflicts in three files. The Skill walks through each hunk, checks the original PRs for intent, resolves them, runs the test suite, and finishes the rebase. ## Quick Start Resolve the current in-progress git merge conflict in this repository, preserving the intent of both branches, then run the project's 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 safely?▼

Start by inspecting the merge state and conflicting files, then trace each change back to its commit message, PR, or issue to understand intent. Resolve each hunk preserving both intents where possible, run the project's typecheck and tests, then stage and commit.

How to finish a rebase after resolving conflicts?▼

After resolving each conflicting hunk, stage the files and continue the rebase until all commits are replayed. Run the project's automated checks first to confirm the resolution did not break anything.

Should I ever use git merge --abort during conflict resolution?▼

This workflow never aborts; it always resolves conflicts in place. Aborting discards progress, so instead resolve each hunk deliberately, choosing the side that matches the merge's stated goal when intents are incompatible.

What checks should run after resolving merge conflicts?▼

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

When should I not use an automated conflict resolution workflow?▼

Avoid it when the conflict involves unclear product decisions that require stakeholder input, since the workflow only chooses between existing intents and never invents new behavior. In those cases, consult the original authors first.