resolving-merge-conflicts

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

1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/jwh3times/holland-vip --skill resolving-merge-conflicts-jwh3times
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/jwh3times/holland-vip --skill resolving-merge-conflicts-jwh3times

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 introducing broken code. 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 - 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 to preserve both intents where possible, choosing the side matching the merge's stated goal when they are incompatible, without inventing new behavior. - Verification and Completion: Runs the project's typecheck, tests, and formatting checks, then stages, commits, and continues the rebase until finished. - Use Case: During a long-running feature branch rebase onto main, conflicts appear in shared modules. Use this Skill to trace each change back to its PR, resolve the hunks correctly, run the test suite, and complete the rebase. ## Quick Start Resolve the current in-progress git merge conflict, verify the project checks pass, 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 correctly?▼

Start by inspecting the conflicted files and git history to understand why each change was made, including commit messages and linked PRs. Resolve each hunk to preserve both intents where possible, then run the project's typecheck, tests, and formatter before committing.

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. Investigate the original intent of each change before choosing how to combine them.

Should I ever use git merge --abort when conflicts are hard?▼

This workflow always resolves conflicts rather than aborting. Aborting discards progress and delays the integration; instead, research the conflicting changes through history and PRs, resolve each hunk, and verify with automated checks.

What checks should I run after resolving merge conflicts?▼

Run the project's automated checks 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 pick one side of a conflict instead of merging both?▼

Pick one side only when the two intents are genuinely incompatible. Choose the change matching the merge's stated goal, note the trade-off, and never invent new behavior that was not part of either original change.