code-resolve-merge-conflicts

Resolve conflicts from an in-progress git rebase or merge using intent-diff analysis.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill code-resolve-merge-conflicts-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-resolve-merge-conflicts
Source: https://github.com/nseng-ai/ns/tree/main/skills/incubating/code/code-resolve-merge-conflicts
Command: npx skills add https://github.com/nseng-ai/ns --skill code-resolve-merge-conflicts-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Resolving merge conflicts during a rebase or merge is error-prone: picking the wrong side, discarding unrelated changes with whole-file checkouts, or continuing with leftover conflict markers can silently corrupt a branch. This Skill provides a disciplined, safe workflow for resolving conflicts from an operation that is already in progress. ## Core Features & Use Cases - Intent-diff resolution: Classifies each conflict against five safe categories (complementary, identical, formatting, rename/API-migration, strict-superset) using the incoming side's actual diff rather than raw conflict markers. - Verification gate: Runs the project's narrowest authoritative validation before continuing, and escalates with a structured payload when a conflict falls outside the safe set. - Driver contract: Acts as the per-conflict engine for driver skills such as code-gt-restack-resolve, with overridable continue command, bail-out conditions, and escalation channel. - Use Case: During a git rebase that stops on three conflicted files, the Skill classifies each conflict, edits only the conflict regions, runs the project checks, and continues the rebase to completion. ## Quick Start Ask the agent to resolve the conflicts in my current in-progress rebase and continue it safely to completion.

Frequently Asked Questions about code-resolve-merge-conflicts

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

FAQPage Schema
How do I resolve git rebase conflicts safely?

Resolve git rebase conflicts by inspecting the intent-diff with git show on the stopped commit, classifying each conflict region, and editing only the conflicted region. Verify with the project's checks before running git rebase --continue, and never use whole-file checkout on files with mixed changes.

What is the difference between merge and rebase conflict markers?

In a merge, the HEAD side is your branch and the incoming ref is the other branch. In a rebase the sides are inverted: HEAD is the new base being rebased onto, and the marked sha is your own commit being replayed.

Can I use this with Graphite gt restack conflicts?

Yes, conflicts from gt restack or gt move are supported. Continue with gt continue instead of git rebase --continue so Graphite's stack bookkeeping stays intact, or use the code-gt-restack-resolve driver skill.

When should a merge conflict be escalated instead of auto-resolved?

Escalate when a conflict falls outside the five safe categories: complementary, identical, formatting-only, explicit rename or API-migration, and one-side strict-superset. The escalation payload includes both sides, the intent-diff, and a proposed resolution with reasoning.

Why should I avoid git checkout --theirs on conflicted files?

Whole-file checkout with --theirs or --ours discards non-conflicting changes elsewhere in the file. It is only acceptable for auto-generated files that will be regenerated afterward; all other files should be edited only within the conflict region.