Agent Skills › zerx-lab/zap › resolve-merge-conflicts

resolve-merge-conflicts

GitHub

通过专用脚本提取冲突文件的上下文和紧凑差异，避免加载完整文件。支持逐个文件解决合并、变基或暂存弹出时的Git冲突，并验证无残留标记。

.agents/skills/resolve-merge-conflicts/SKILL.md zerx-lab/zap

Trigger Scenarios

Git merge/rebase/cherry-pick/stash pop 遇到冲突 git status 显示未合并路径文件中包含冲突标记

Install

npx skills add zerx-lab/zap --skill resolve-merge-conflicts -g -y

More Options

Non-standard path

npx skills add https://github.com/zerx-lab/zap/tree/main/.agents/skills/resolve-merge-conflicts -g -y

Use without installing

npx skills use zerx-lab/zap@resolve-merge-conflicts

指定 Agent (Claude Code)

npx skills add zerx-lab/zap --skill resolve-merge-conflicts -a claude-code -g -y

安装 repo 全部 skill

npx skills add zerx-lab/zap --all -g -y

预览 repo 内 skill

npx skills add zerx-lab/zap --list

SKILL.md

Frontmatter

{
    "name": "resolve-merge-conflicts",
    "description": "Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers."
}

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

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.

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.

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.

Re-check unresolved files.

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

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.