All Agent Skills

Codemattpocock-skills

resolving-merge-conflicts

Use when you need to resolve an in-progress git merge/rebase conflict.

11.5k est. installs237.3k stars

Estimated installs are a discovery signal based on public repository popularity and source completeness, not recorded Dokki installation events.

Skill provenance

Repository

mattpocock/skills

Pinned commit

6654f6b60cd9

License

MIT

Execution

Instructions only

Complete source instructions

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. 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.

Same repository

Start your company of agents
today.

Free to start. Your first team is one sentence away.