resolving-merge-conflicts

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

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill resolving-merge-conflicts-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill resolving-merge-conflicts-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are often resolved hastily, losing one side's intent or introducing regressions. This Skill provides a disciplined workflow to understand each conflicting change, resolve hunks correctly, and verify 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 run git rebase main on a long-lived feature branch and hit conflicts across five files. The Skill walks through each hunk, checks the original PRs for intent, resolves them, runs the test suite, and finishes the rebase cleanly. ## Quick Start Resolve the current 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 git merge conflicts without losing changes?▼

Resolve git merge conflicts by first understanding why each side changed the code, using commit messages, PRs, and original tickets. Then resolve each hunk to preserve both intents where possible, and run the project's tests to confirm nothing broke.

How to resolve conflicts during a git rebase?▼

During a git rebase, resolve each conflicted file by examining the conflicting hunks and their original intent, stage the resolved files, and continue the rebase until all commits are replayed. Never abort midway; always finish the rebase process.

Should I run tests after resolving merge conflicts?▼

Yes, always run the project's automated checks after resolving conflicts, typically typecheck first, then tests, then formatting. Conflict resolution can silently break logic even when the code compiles, so verification is essential before committing.

When should I abort a merge instead of resolving conflicts?▼

This workflow never aborts; it always resolves conflicts and completes the merge or rebase. Aborting discards progress and leaves the underlying divergence unaddressed, so resolution with proper intent analysis is preferred.

What are the limitations of automated merge conflict resolution?▼

Automated resolution cannot invent new behavior or guess business intent when two changes are fundamentally incompatible. In such cases it picks the change matching the merge's stated goal and notes the trade-off for human review.