resolving-merge-conflicts

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

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/clementcaron-resolving-merge-conflicts

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

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

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/resolving-merge-conflicts

What's inside

Skill name: resolving-merge-conflicts
Description: Use when you need to resolve an in-progress git merge/rebase conflict.
License: MIT
Instructions: 11 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
SKILLS.md

SKILL.md (first lines)

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. **Stop at a clean handoff point.** Once every conflict is resolved and the relevant checks are green, summarise any manual git commands still required to finish the merge or rebase. Leave staging, committing, and rebase continuation to the user unless they explicitly ask you to perform them.

From clementcaron/skills, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Jun 17, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/clementcaron/skills
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from clementcaron

Cite this page

resolving-merge-conflicts skill. Agent Mart. https://agentmart.dev/skills/clementcaron-resolving-merge-conflicts (last updated 2026-10-24)