fix-merge-conflicts

Identify and resolve in-progress git merge or rebase conflicts.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/vathymut/copilot-skills --skill fix-merge-conflicts-vathymut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-merge-conflicts
Source: https://github.com/vathymut/copilot-skills/tree/main/.github/skills/fix-merge-conflicts
Command: npx skills add https://github.com/vathymut/copilot-skills --skill fix-merge-conflicts-vathymut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of resolving in-progress git merge or rebase conflicts, ensuring the working tree remains in a clean and consistent state.

Core Features & Use Cases

  • Conflicts Resolution: Identifies and resolves merge conflicts by preserving the intent behind each conflicting side.
  • Validation: Validates the result of the conflict resolution to ensure no conflicts remain and that the application can be built successfully.
  • Use Case: When a developer encounters a merge conflict while integrating changes from a feature branch, this Skill guides them through the resolution process and completes it safely.

Quick Start

To resolve a merge conflict using the fix-merge-conflicts skill, first check the status with git status, then run the skill to guide you through the resolution steps.

Frequently Asked Questions about fix-merge-conflicts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve git merge conflicts step by step?

To resolve git merge conflicts, identify the conflicting files using git status, preserve the intent behind each side, validate the resolution to ensure no conflicts remain, and complete the merge process to keep the working tree consistent.

What is the best way to fix a rebase conflict in git?

The best way to fix a git rebase conflict is to identify the in-progress conflicts, resolve them by preserving both sides' intent, validate the result, and complete the rebase to maintain a clean working tree state.

Why does my git working tree remain inconsistent after a merge conflict?

Your working tree remains inconsistent because the merge conflict resolution is incomplete. You must resolve all identified conflicts, validate that no conflicts remain, and ensure the application builds successfully before completing the merge.

How do I validate conflict resolution before completing a git merge?

To validate conflict resolution before completing a git merge, check that no conflicts remain in the working tree and verify that the application can be built successfully to ensure the final state is consistent.

Can I use a script to automatically resolve in-progress git merge conflicts?

Yes, you can use a script to automatically resolve in-progress git merge conflicts. The script identifies conflicts, guides you through step-by-step resolution, validates the result, and completes the merge or rebase process safely.