resolving-merge-conflicts

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill resolving-merge-conflicts-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/falentio/cimi --skill resolving-merge-conflicts-falentio

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 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-Preserving Resolution: Traces each conflict back to commits, PRs, and original issues so both intents are preserved where possible, with trade-offs noted when they are incompatible. - Verification and Completion: Runs the project's typecheck, tests, and formatting checks, then stages, commits, and continues the rebase until finished. - Use Case: You are mid-rebase of a long-lived feature branch onto main and hit conflicts in five files. Use this Skill to understand why each side changed, resolve every hunk without inventing new behavior, run the test suite, and complete the rebase cleanly. ## Quick Start Resolve the current git merge conflict in my repository, preserving both sides' intent, 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 without losing changes?

Inspect the merge state and conflicting files first, then trace each change back to its commit, PR, or issue to understand intent. Resolve each hunk preserving both intents where possible, and run the project's typecheck and tests before committing.

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. Run the project's automated checks such as typecheck and tests to confirm nothing broke during the rebase.

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

Both produce conflicts when branches diverge; the resolution workflow is the same. Merge preserves branch history with a merge commit, while rebase replays commits linearly and may require resolving conflicts across multiple commits.

When should I abort a merge instead of resolving conflicts?

This workflow never aborts: it always resolves conflicts rather than running git merge --abort. Aborting discards progress; instead, resolve each hunk based on the merge's stated goal and note any trade-offs.

Why do merge conflict resolutions break the build?

Resolutions break builds when hunks are combined mechanically without understanding semantic dependencies between changes. Running typecheck, tests, and format checks after resolving catches these breakages before committing.