mcpbeat

Resolving Merge Conflicts

google/resolving-merge-conflicts

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

258 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
1
copies elsewhere
how many repositories repackaged it
1
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/google/tf-remote-vars --skill resolving-merge-conflicts

What comes with it

113 bytes besides the instruction
agents/openai.yaml

The instruction itself

as written by the author
  • See the current state of the merge/rebase. Check git history, and the conflicting files.
  • 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.
  • 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.
  • Discover the project's automated checks and run them — typically typecheck, then tests, then format. Fix anything the merge broke.
  • Finish the merge/rebase. Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.

Repackaged in 1 other repositories

same content, different owner
aiskillstore/marketplace open on GitHub →

How to use it

Copy the folder

Take google/resolving-merge-conflicts from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.