mcpField
F
fix-merge-conflicts

fix-merge-conflicts

github.com/cursorDevelopment14.5k2.7k installsUpdated today
Repository

About fix-merge-conflicts

fix-merge-conflicts is a development skill for resolving Git merge conflicts with minimal, correctness-focused changes. It checks the resulting code with compilation, linting, and relevant tests, then stages the resolved files and summarizes decisions.

Key features

  1. 01Finds conflicted files and markers
  2. 02Resolves conflicts with minimal edits
  3. 03Regenerates lockfiles with package tools
  4. 04Runs compile, lint, and relevant tests
  5. 05Stages resolved files and reports choices

Use cases

  1. 01Restoring a buildable state after a merge
  2. 02Resolving conflicts while preserving behavior
  3. 03Checking changes before staging resolutions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cursor/plugins --skill fix-merge-conflicts

After installing, type/fix-merge-conflictsin Claude Code to confirm it loaded.

Details

From the project README

Fix merge conflicts

Trigger

Branch has unresolved merge conflicts and needs a reliable path to a buildable state.

Workflow

  1. Detect all conflicting files from git status and conflict markers.
  2. Resolve each conflict with minimal, correctness-first edits.
  3. Prefer preserving both sides when safe. Otherwise, choose the variant that compiles and keeps public behavior stable.
  4. Regenerate lockfiles with package manager tools instead of hand-editing.
  5. Run compile, lint, and relevant tests.
  6. Stage resolved files and summarize key decisions.

Guardrails

  • Keep changes minimal and readable.
  • Do not leave conflict markers in any file.
  • Avoid broad refactors while resolving conflicts.
  • Do not push or tag during conflict resolution.

Output

  • Files resolved
  • Notable resolution choices
  • Build/test outcome

Comments

Markdown supported