resolve-conflict

Detects, analyzes, and safely resolves git merge conflicts with user confirmation.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/Cohey0727/CodingAgentTools --skill resolve-conflict-cohey0727
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-conflict
Source: https://github.com/Cohey0727/CodingAgentTools/tree/main/skills/resolve-conflict
Command: npx skills add https://github.com/Cohey0727/CodingAgentTools --skill resolve-conflict-cohey0727

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge conflicts during git merges, rebases, and cherry-picks are error-prone to fix by hand, and a wrong resolution can silently delete someone's work. This Skill guides the AI through a structured workflow that detects conflicts, analyzes both sides' intent, and resolves them only after your approval. ## Core Features & Use Cases - Conflict Detection & Analysis: Identifies conflicted files with git diff --name-only --diff-filter=U and inspects ours/theirs/ancestor versions via git show :1: :2: :3: to understand each side's intent. - Guided Resolution with Approval: Presents a per-conflict summary (ours vs theirs, recommendation, reason) and waits for your confirmation before editing anything. - Safe Verification & Staging: Verifies no conflict markers remain, runs git diff --check, stages files individually, and never auto-commits or aborts operations. - Use Case: During a rebase of a feature branch, both sides modified the same function. The Skill merges caching logic from one side with error handling from the other, shows you the combined result, and stages it only after you approve. ## Quick Start Resolve the merge conflicts in my current git rebase, showing me each conflict and your recommended resolution before applying it.

Frequently Asked Questions about resolve-conflict

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve git merge conflicts safely?▼

List conflicted files with git diff --name-only --diff-filter=U, then inspect each side using git show :2:file (ours) and :3:file (theirs). Edit files to remove conflict markers while preserving both sides' intent, verify with git diff --check, and stage files individually.

How to see both sides of a git merge conflict?▼

Use git show :1:file for the common ancestor, :2:file for our version, and :3:file for their version. Running git log --oneline --merge -- file also shows which commits on each side touched the conflicted file.

Should I manually resolve conflicts in package-lock.json?▼

No, lock files like package-lock.json and yarn.lock should not be merged by hand. Check out one side with git checkout --theirs package-lock.json, then regenerate the file by running npm install so the dependency tree stays consistent.

Can git conflicts be resolved automatically without review?▼

This workflow never auto-resolves conflicts; it presents each conflict with a recommendation and waits for explicit user confirmation before editing. It also refuses to run git merge --abort, git rebase --abort, or whole-file checkout --ours/--theirs without approval.

What should I do after resolving all merge conflicts?▼

Verify no conflict markers remain with git diff --check, stage each resolved file individually with git add, then run git status to confirm. For a merge you can commit, for a rebase run git rebase --continue, and for a cherry-pick run git cherry-pick --continue.