mcpField
R
resolving-merge-conflicts

resolving-merge-conflicts

github.com/mattpocockDevelopment305.7k551.1k installsUpdated 1d ago
Repository

About resolving-merge-conflicts

resolving-merge-conflicts is a skill for developers handling merge or rebase conflicts. It guides investigation of each change's intent, conflict resolution, automated checks, and completion of the operation.

Key features

  1. 01Inspect merge or rebase state
  2. 02Trace the intent behind changes
  3. 03Resolve hunks while preserving intent
  4. 04Run project checks and fix regressions
  5. 05Complete the merge or rebase

Use cases

  1. 01Resolving conflicts during a merge
  2. 02Handling conflicts while rebasing commits
  3. 03Checking a project after conflict resolution

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mattpocock/skills --skill resolving-merge-conflicts

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

Bundled filesagents/openai.yaml

Details

From the project README

  1. See the current state of the merge/rebase. Check git history, and the conflicting files.

  2. Find the primary sources for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues/tickets.

  3. Resolve each hunk. Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do not invent new behaviour. Always resolve; never --abort.

  4. Discover the project's automated checks and run them, typically typecheck, then tests, then format. Fix anything the merge broke.

  5. Finish the merge/rebase. Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.

Comments

Markdown supported