resolving-merge-conflicts

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill resolving-merge-conflicts-the-focus-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/The-Focus-AI/walking-thoughts/tree/main/.agents/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill resolving-merge-conflicts-the-focus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are often resolved hastily, losing the intent behind one side of the change. This Skill provides a disciplined workflow for understanding each conflict's origin, resolving hunks without inventing new behavior, and finishing the merge safely. ## Core Features & Use Cases - Conflict Investigation: Inspects git history, commit messages, PRs, and original issues to understand why each conflicting change was made. - Intent-Preserving Resolution: Resolves each hunk by preserving both intents where possible, or choosing the side matching the merge's stated goal while noting trade-offs. - Verification and Completion: Runs the project's automated checks (typecheck, tests, format), fixes merge breakage, then stages, commits, and continues the rebase to completion. - Use Case: During a long-running feature branch rebase onto main, conflicts appear in five files. The Skill traces each conflict to its source PR, resolves hunks without dropping either feature's logic, runs the test suite, and completes 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 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?

Resolve a git merge conflict by first inspecting the conflicting files and git history to understand each side's intent. Then resolve each hunk preserving both intents where possible, run the project's typecheck and tests, and stage and commit the result.

How to continue a rebase after fixing conflicts?

After resolving conflicting hunks in each file, stage the resolved files and continue the rebase process until all commits are rebased. Run the project's automated checks before finishing to catch anything the merge broke.

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

Both operations can produce conflicts, and the resolution approach is the same: understand each change's origin, resolve hunks without inventing new behavior, and verify with tests. The choice depends on your team's history preferences, not conflict handling.

When should I abort a merge instead of resolving it?

This workflow never aborts: it always resolves the conflict rather than running git merge --abort or rebase --abort. If intents are incompatible, it picks the side matching the merge's stated goal and records the trade-off.

Why do merge conflicts keep breaking my tests after resolution?

Conflicts resolved syntactically can still break semantics when two changes interact. Running the project's full checks—typecheck, then tests, then format—after resolution catches this breakage before the merge is committed.