FI

fix-conflicts

Identifies and resolves Git conflicts through automated state detection and history analysis.

Install

mkdir -p .claude/skills/fix-conflicts && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13113" && unzip -o skill.zip -d .claude/skills/fix-conflicts && rm skill.zip

Installs to .claude/skills/fix-conflicts

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when git reports merge conflicts, rebase conflicts, cherry-pick conflicts, or revert conflicts, or when the user asks to resolve conflicts. Triggers: \"fix conflicts\", \"resolve conflicts\", \"merge conflicts\", \"rebase conflicts\", \"fix merge\", \"resolve merge\", \"help with conflicts\", \"conflict markers\".
319 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • →Detect the type of Git conflict (merge, rebase, revert, cherry-pick)
  • →Identify conflicted files and their conflict types
  • →Read conflicted files and focus on conflict markers
  • →Gather local and remote commit history for context
  • →Inspect commit diffs to understand intent
  • →Resolve standard conflicts by merging, combining, or choosing sides

How it works

The skill detects the conflict state, reads conflicted files, gathers commit history to understand intent, and then resolves conflicts based on type and intent, reporting the results.

Inputs & outputs

You give it
A Git repository in a conflicted state
You get back
Files with conflict markers resolved, and a summary report of resolutions

When to use fix-conflicts

  • →Fixing merge conflicts
  • →Resolving rebase conflicts
  • →Fixing cherry-pick conflicts

About fix-conflicts

Detects the type and location of Git conflicts by inspecting the current working state. It guides users through resolving markers by providing contextual diff history from both local and remote branches.

Use when git reports merge conflicts, rebase conflicts, cherry-pick conflicts, or revert conflicts, or when the user asks to resolve conflicts. Triggers: \"fix conflicts\", \"resolve conflicts\", \"merge conflicts\", \"rebase conflicts\", \"fix merge\", \"resolve merge\", \"help with conflicts\", \"

When not to use it

  • →When there are no Git conflicts to resolve
  • →When the user explicitly wants to continue the Git operation automatically
  • →When the user wants to re-add intentionally deleted code

Limitations

  • →Never automatically run `git merge --continue` or similar commands
  • →Does not re-add intentionally deleted code
  • →Semantic conflicts (compiles but logically wrong) are flagged as risks

How it compares

This skill provides a structured, analytical approach to resolving Git conflicts by examining commit history and intent, rather than simply choosing 'ours' or 'theirs' blindly.

Compared to similar skills

fix-conflicts side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
fix-conflicts (this skill)04moReviewAdvanced
resolve-conflicts8110moReviewIntermediate
dependency-upgrade266moReviewIntermediate
openspec-onboard108moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry