Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
warpdotdev avatar

Resolve Merge Conflicts

  • 16.2k installs
  • 148 repo stars
  • Updated July 24, 2026
  • warpdotdev/common-skills

How to inspect and resolve Git merge conflicts without loading full files into context, using a Python script to extract only unresolved paths and conflict hunks.

About

This skill provides a Python script that extracts unresolved merge conflicts without loading entire files into context. It generates a summary of conflicted paths and their conflict hunks, then allows drilling into individual files to view compact diffs between ours/theirs versions. Developers use it when merges, rebases, cherry-picks, or stash pops stop on conflicts. The workflow prioritizes minimal context by showing only nearby conflict regions and unified diffs, then prompts resolution via git checkout or direct editing, followed by validation to ensure no markers remain.

  • Extracts conflict summary showing unresolved paths, index stages, and hunk counts without loading full files
  • Drills into one conflicted file at a time with compact unified diff between ours and theirs sections
  • Provides JSON output and tunable context window (lines and surrounding context) for flexible inspection
  • Handles both marker-based text conflicts and index-only conflicts like add/add or modify/delete
  • Integrated workflow: summarize, inspect, resolve with git checkout or manual edit, re-check, validate markers removed

Resolve Merge Conflicts by the numbers

  • 16,187 all-time installs (skills.sh)
  • +1,947 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #6 of 739 Git & Pull Requests skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

resolve-merge-conflicts capabilities & compatibility

Capabilities
extract unresolved conflict paths · view compact conflict hunks per file · generate unified diffs (ours vs theirs) · provide json structured output · summarize conflict metadata · validate markers removed
Works with
github · gitlab · bitbucket
Use cases
code review · debugging
Platforms
macOS · Windows · Linux · WSL
Runs
Runs locally
Pricing
Free
From the docs

What resolve-merge-conflicts says it does

Resolve conflicts without opening full files unless the compact view is insufficient. Start with a summary, then inspect one conflicted file at a time.
resolve-merge-conflicts.md overview
npx skills add https://github.com/warpdotdev/common-skills --skill resolve-merge-conflicts

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs16.2k
repo stars148
Security audit3 / 3 scanners passed
Last updatedJuly 24, 2026
Repositorywarpdotdev/common-skills

What it does

Extract and resolve Git merge conflicts efficiently by viewing only unresolved paths and compact diffs instead of loading full files.

Who is it for?

Developers resolving merge conflicts during code integration, rebase workflows, or stash operations who need to keep context lean.

Skip if: Automated conflict resolution without human judgment; large binary conflicts; workflows that require full file context.

When should I use this skill?

git status shows unmerged paths, merge/rebase/cherry-pick/stash pop stops, or files contain conflict markers.

What you get

Conflicts resolved with minimal context overhead, validated for marker removal, and staged for commit.

  • Conflict summary report
  • Per-file conflict detail view
  • JSON output of conflicts

By the numbers

  • Script shows only nearby context and conflict hunks, not full files
  • Supports tunable context window (--context 3, --max-lines 60)
  • Handles both marker-based and index-only conflicts (add/add, modify/delete)

Files

SKILL.mdMarkdownGitHub ↗

Resolve Merge Conflicts

Overview

Resolve conflicts without opening full files unless the compact view is insufficient. Start with a summary, then inspect one conflicted file at a time.

Workflow

1. Start with a summary.

python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py

Use the summary to identify which files are unresolved, which index stages exist, and how many text hunks each file contains.

2. Drill into one file.

python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py --file path/to/file

Prefer this over reading the whole file. The script prints only nearby context, the ours / base / theirs sections for each hunk, and a compact unified diff between ours and theirs.

3. Resolve the file.

  • Take one side wholesale with git checkout --ours -- path/to/file or git checkout --theirs -- path/to/file when appropriate.
  • Otherwise edit the file directly and remove the conflict markers.
  • Read more of the file only if the compact output is not enough to decide the correct merge.

4. Re-check unresolved files.

python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py
git diff --name-only --diff-filter=U

5. Validate the resolution.

  • Ensure no unmerged paths remain.
  • Ensure no <<<<<<<, =======, or >>>>>>> markers remain in the resolved files.
  • Run targeted tests, builds, or linters for the touched area.
  • Stage the resolved files.

Commands

Summary only

python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py

Detailed view for one file

python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py --file path/to/file

Detailed view for all conflicted files

python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py --all

JSON output

python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py --file path/to/file --json

Tune output size

python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py \
  --file path/to/file \
  --context 3 \
  --max-lines 60

Notes

  • Use the script before opening conflicted files directly.
  • Resolve one file at a time to keep context small.
  • Expect marker-based text conflicts and index-only conflicts such as add/add or modify/delete. The script summarizes both, and it falls back to index-stage previews when the worktree file has no conflict markers.

Related skills

How it compares

Use resolve-merge-conflicts for structured conflict context extraction; use review-pr when the branch is already clean and ready for spec-based PR review.

FAQ

When should I use this skill?

Use it after a merge, rebase, cherry-pick, or stash pop fails with conflicts, or when git status shows unmerged paths.

What output does the summary provide?

It lists unresolved paths, which index stages exist for each file, and the count of text hunks in each conflicted file.

Can I resolve without reading the whole file?

Yes. The script shows compact context around each conflict hunk and unified diff between ours/theirs. Only open the full file if this is insufficient.

Is Resolve Merge Conflicts safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.