fix-merge-conflicts — Claude Code skill
Resolves merge conflicts in a branch, then checks the build and tests before wrapping up. Use it when several conflicted files need focused fixes without a refactor.
npx skills add cursor/plugins --skill fix-merge-conflicts -a claude-codeWhat fix-merge-conflicts does
The skill finds conflicted files through git status and conflict markers, then applies small corrections with correctness as the priority. It keeps changes from both sides when that is safe; otherwise it selects the version that compiles and preserves public behaviour.
Lockfiles are regenerated with package-manager tools rather than edited by hand. The workflow then runs the build, linting, and relevant tests. Resolved files are staged, followed by a summary of the main decisions.
It does not push changes or create tags. You still need to handle the final branch push yourself.
What it helps with
- find every file with a merge conflict
- remove conflict markers from source files
- retain compatible changes from both branches
- regenerate lockfiles with package-manager tools
- check the build and relevant tests
Example prompts for the agent
- Use `fix-merge-conflicts` to resolve conflicts in the current branch.
- Run `fix-merge-conflicts` and validate the build after the fixes.
- Use `fix-merge-conflicts` to handle conflicted files, regenerate lockfiles, and stage the resolved changes.
How to install fix-merge-conflicts
1Skills CLI (Vercel)
npx skills add cursor/plugins --skill fix-merge-conflicts -a claude-code2Manually: put the files in place
~/.claude/skills/fix-merge-conflicts/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fix-merge-conflicts/
1Skills CLI (Vercel)
npx skills add cursor/plugins --skill fix-merge-conflicts -a codex2Manually: put the files in place
.agents/skills/fix-merge-conflicts/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cursor/plugins --skill fix-merge-conflicts -a cursor2Manually: put the files in place
.cursor/skills/fix-merge-conflicts/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cursor/plugins fix-merge-conflicts2Manually: put the files in place
.github/skills/fix-merge-conflicts/SKILL.md1Skills CLI (Vercel)
npx skills add cursor/plugins --skill fix-merge-conflicts -a gemini-cli2Platform CLI
gemini skills install https://github.com/cursor/plugins --path cursor-team-kit/skills/fix-merge-conflictsManually: put the files in place
.devin/skills/fix-merge-conflicts/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cursor/plugins --skill fix-merge-conflicts -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set18
The whole set →Similar
Questions about fix-merge-conflicts
How do I install fix-merge-conflicts in Claude Code?
Run npx skills add cursor/plugins --skill fix-merge-conflicts -a claude-code, then run npx skills add cursor/plugins --skill fix-merge-conflicts -a claude-code again. The skill file is placed at ~/.claude/skills/fix-merge-conflicts/SKILL.md.
What does fix-merge-conflicts do?
It detects merge conflicts, resolves them with minimal edits, and checks the result with a build, linting, and relevant tests. It then stages resolved files and reports the decisions made.
Does fix-merge-conflicts push changes to the remote repository?
No. The skill does not push changes or create tags while resolving conflicts.