resolving-merge-conflicts

Originally frommattpocock/skills
Installation
SKILL.md
  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. Default to resolving; reach for --abort only when the two intents are irreconcilable and the right fix is restructuring the change.

  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.

Installs
106
GitHub Stars
161
First Seen
Jul 14, 2026
resolving-merge-conflicts — tt-a1i/matt-skills-with-to-goal