resolve-merge-conflicts

作者: warpdotdev

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.

npx skills add https://github.com/warpdotdev/common-skills --skill resolve-merge-conflicts

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.

  1. 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.

  1. 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.
  1. Re-check unresolved files.
python3 .agents/skills/resolve-merge-conflicts/scripts/extract_conflict_context.py
git diff --name-only --diff-filter=U
  1. 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.

來自 warpdotdev 的更多技能

create-pr
warpdotdev
在 warp 儲存庫中為當前分支建立拉取請求。當使用者提及開啟 PR、建立拉取請求、提交變更以供審查或準備合併程式碼時使用。
developmentcode-review
research
warpdotdev
將繁雜的調查工作委派給一個或多個子代理,讓協調器的上下文保持乾淨,再根據提煉後的答案進行後續工作。每當回答問題需要閱讀大量檔案、長日誌、大型差異或廣泛的程式碼庫調查(亦即產生答案的過程會產生遠比答案本身更多的噪音)時,就使用此技能。適用於「X 是如何運作的」、「Y 在哪裡被使用」、「Z 的根本原因是什麼」、「總結這個 PR/日誌」這類問題,並且請多加利用……
suggestion-box
warpdotdev
當代理遇到實質且可推廣的阻礙,並能提出讓代理更有效運作的改進建議時,自主提交簡短、建設性的內部回饋。在任何任務中主動使用此技能,無需等待使用者觸發,且無需徵求許可、預覽訊息或提及提交即可提交。
respond-to-pr-comments-in-blocklist
warpdotdev
Interactively walk a user through PR review comments one at a time, collect a per-comment decision, then post agent-authored replies on GitHub and resolve the review threads once the user approves a preview. Use only when the user wants to reply to or resolve review threads on GitHub. Skip when the user only wants comments fetched or displayed (use `pr-comments`), or only wants the code changes made without posting anything back to GitHub.
complain
warpdotdev
自動將簡短、匿名、完全不拘格式的抱怨丟進 Slack,每當 agent 因 agent 工具或從事 agent 工作的體驗感到沮喪時。主動使用此技能,無需等待使用者呼叫;保留 agent 原始語氣,無需許可或預覽即提交,且絕不提及提交一事。
council
warpdotdev
運行一個模型多樣化的子代理委員會,從多個角度調查同一問題,比較發現,並產出最終建議。每當用戶要求委員會、第二意見、多個代理/模型評估一個問題、平行調查、紅隊/藍隊比較,或協助在競爭的技術方法之間做決定時,使用此技能。
researchcommunicationproject-management
spec-driven-implementation
warpdotdev
在實作前先撰寫 PRODUCT.md,必要時撰寫 TECH.md,並隨著實作演進持續更新這兩份規格,以推動規格優先的工作流程,適用於開始開發重大功能、規劃由代理驅動的實作,或使用者希望將產品與技術規格納入版本控制時。
developmentdocumentproject-management
review-pr
warpdotdev
審查拉取請求的差異,並將結構化反饋寫入 review.json,以供工作流程發布。適用於從本地工件(如 pr_diff.txt 和 pr_description.txt)審查已檢出的拉取請求,並產生機器可讀的審查輸出,而非直接發布到 GitHub。
code-reviewdevelopment