resolving-merge-conflicts

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/pd-phuc/laravel-template --skill resolving-merge-conflicts-pd-phuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/pd-phuc/laravel-template/tree/main/.claude/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/pd-phuc/laravel-template --skill resolving-merge-conflicts-pd-phuc

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 - Conflict Investigation: Inspects the current merge/rebase state, git history, commit messages, PRs, and original issues to understand why each change was made. - Intent-Preserving Resolution: Resolves each conflicting hunk by preserving both intents where possible, choosing the side matching the merge's stated goal when they are incompatible, and never aborting the merge. - Verification and Completion: Discovers and runs the project's automated checks (typecheck, tests, formatting), fixes anything the merge broke, then stages, commits, and continues the rebase to completion. - Use Case: During a long-running feature branch rebase onto main, multiple files conflict. The Skill traces each conflict back to its originating commits and tickets, resolves them coherently, runs the test suite, and finishes the rebase. ## Quick Start Resolve the current git merge conflict in this repository, verify the project checks pass, and complete 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: read the commit messages, PRs, and original tickets. Then resolve each hunk preserving both intents where possible, and run the project's tests and typecheck before committing.

How to continue a git rebase after fixing conflicts?▼

After resolving the conflicting files, stage them with git add and run git rebase --continue. Repeat the process for each conflicting commit until the rebase finishes, and run the project's automated checks to confirm nothing broke.

Should I use git merge or git rebase for integrating branches?▼

Both create conflicts when the same lines change on each side. Merge preserves branch history with a merge commit, while rebase replays commits for a linear history; the resolution workflow of inspecting intent and verifying with tests applies to either.

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

This workflow never aborts: it always resolves conflicts by tracing each change to its source and picking the side matching the merge's stated goal when intents are incompatible. Aborting discards progress and leaves the integration problem unsolved.

Why do merge conflicts keep breaking my build after resolution?▼

Conflicts resolved textually can still break semantics, such as duplicate definitions or incompatible logic. Always run the project's automated checks after resolving: typecheck first, then tests, then formatting, and fix anything the merge broke before committing.