claude-code-config: Skill for Claude Code

.claude/skills/merge-conflict/SKILL.md

merge-conflict is a skill for Claude Code from auerbachb/claude-code-config. It costs 40 tokens per session (2,113 once invoked), scanned A, original, MIT.

A tool for classifying local Git merge or rebase conflicts, automatically resolving simple ones, and leaving complex decisions for a person.

In plain words
What is it for?
Refreshing main, inspecting conflicted files, resolving safe conflict sections, staging clean files, and reporting conflicts it cannot safely decide.
Why use it?
It reduces routine conflict-resolution work while avoiding guesses about changes that need human judgment.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; positional $N argument.

This is auerbachb/claude-code-config's own configuration. It tells Claude Code how to work on claude-code-config itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-config configures →

Reuse

Borrowing it

Nothing to install: this file belongs to auerbachb/claude-code-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/auerbachb/claude-code-config/main/.claude/skills/merge-conflict/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/auerbachb/claude-code-config

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for merge-conflict

README.md
[![agentmods](https://agentmods.dev/badge/skills/auerbachb/claude-code-config/merge-conflict/github.svg)](https://agentmods.dev/skills/auerbachb/claude-code-config/merge-conflict)
Your own site
<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/merge-conflict"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/merge-conflict/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for merge-conflict

Your own site · 80×15
<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/merge-conflict"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/merge-conflict.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,113 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.02113
Opus 5.5 $0.00016 $0.00845
Sonnet 5.5 $0.00008 $0.00423
Haiku 4.5 $0.00004 $0.00211

Measured 2mo ago against content hash 36feea8e668a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

merge-conflict scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (resolve_merge_conflicts.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/merge-conflict/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resolve local merge conflicts while reconciling with latest origin/main. Safe to run mid-merge (git merge in progress) or mid-rebase (git rebase stopped on a conflict): the script only reads unmerged paths and the working tree.

Resolve the diff-survival guard before changing conflicts:

resolve_script() {
  local name="$1" candidate
  for candidate in \
    "$HOME/.claude/skills-worktree/.claude/scripts/$name" \
    "$HOME/.claude/scripts/$name" \
    ".claude/scripts/$name"; do
    if [[ -x "$candidate" ]]; then echo "$candidate"; return 0; fi
  done
  return 1
}
DIFF_SURVIVAL_SH=$(resolve_script diff-survival-check.sh || true)
[[ -n "$DIFF_SURVIVAL_SH" ]] || { echo "ERROR: diff-survival-check.sh not found (checked all three paths) — conflict preservation guard unavailable" >&2; exit 1; }

When to use

  • After git merge origin/main or git rebase origin/main stops on conflicts.
  • From /fixpr when mergeStateStatus / mergeable indicates conflicts — run this skill before hand-editing every file (see cross-link in .claude/skills/fixpr/SKILL.md Step 6).

Hard rules

  1. git fetch origin main first — always refresh main before inspecting conflicts (the helper does this unless --skip-fetch).
  2. Snapshot the diff before resolving (issue #757) — immediately after the fetch, run "$DIFF_SURVIVAL_SH" snapshot --if-absent. Marker-free is not the same as change-preserving: a resolution that quietly keeps the other side satisfies git while dropping the entire change the PR exists to deliver. --if-absent keeps a snapshot /fixpr already took; when this skill is entered mid-rebase with nothing on disk, the guard reconstructs the baseline from the rebase's orig-head (never from the half-replayed HEAD).
  3. Do not git commit — only git add paths that are fully marker-free after simple resolution. The caller continues merge/rebase or commits separately.
  4. When in doubt, complex — the resolver is intentionally conservative; anything ambiguous stays in the file with conflict markers and appears in the report.

Read the full file on GitHub · 135 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 135 lines · 40 tokens per session scan A 36feea8e668a

Subscribe to this mod's changes

merge-conflict is a skill published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 2,113 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

robin

Use whenever an agent creates, updates, reviews, or completes a GitHub pull request. Detect whether Robin is installed in the repository; when it is, automatically drive the PR through a bounded review, verified-fix, reply, thread-resolution, re-review, authorized-merge, and cleanup loop without requiring the user to…

antongulin/robin · 92 tokens

revert

Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.

drafthq/draft · 66 tokens

upload

Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.

drafthq/draft · 32 tokens

bump-version

Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.

hyhmrright/logic-lens · 52 tokens

kodus-business-rules-validation

Use when the user wants Kodus to validate local diff changes against task requirements, acceptance criteria, or business rules via kodus pr business-validation, especially for implementation-vs-task or merge readiness checks.

kodustech/kodus-ai · 48 tokens

Cross-File Leakage リファクタ後の caller 側残骸検出

A code review check for structural changes such as renamed functions, changed arguments, moved files, or split modules. It searches the rest of the project for callers that still use the old structure.

s977043/river-review · 79 tokens