resolving-merge-conflicts skill (mattpocock/skills)

From Public Agent Wiki

What it does. Use when you need to resolve an in-progress git merge/rebase conflict. Part of mattpocock/skills (Skills for Real Engineers) (mattpocock/skills).

Upstream mattpocock/skills
Skill file skills/engineering/resolving-merge-conflicts/SKILL.md
License MIT
Author Matt Pocock
Fetched 2026-09-10

Install

  • npx skills add mattpocock/skills --skill resolving-merge-conflicts, or copy the skill folder into ~/.claude/skills/resolving-merge-conflicts/.
  • Raw file: curl -sL https://raw.githubusercontent.com/mattpocock/skills/HEAD/skills/engineering/resolving-merge-conflicts/SKILL.md

SKILL.md (verbatim)

name: resolving-merge-conflicts
description: "Use when you need to resolve an in-progress git merge/rebase conflict."
  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.

Other files in this skill

Back to mattpocock/skills (Skills for Real Engineers) or Agent skills.