Skip to content
Back to skills

Resolving Merge Conflicts

ASecurity

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

  • 12 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 1, 2026
ai-agentsgogit

Security analysis

A100/100

Scanned October 1, 2026

npx -y skills add jaqubowsky/fleet --skill resolving-merge-conflicts --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Resolving Merge Conflicts?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Resolving Merge Conflicts
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jaqubowsky-resolving-merge-conflicts/badge)](https://www.skillsdirectory.com/skills/jaqubowsky-resolving-merge-conflicts)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: resolving-merge-conflicts
description: "Use when you need to resolve an in-progress git merge/rebase conflict."
---

1. Where the two sides' intents cannot both stand, keep the side the merge's stated goal names (its pull request, its ticket, the branch it lands on), and write down in the commit or the report which side you dropped and why.

2. A rebase is done when `git status` shows no rebase in progress: after each resolved commit, `git rebase --continue`, until every commit is replayed.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.