About fix-merge-conflicts
A skill for resolving merge conflicts while keeping changes minimal and the branch buildable. It guides conflict detection, correctness-first edits, dependency lockfile regeneration, and compile, lint, and test checks.
Key features
- 01Detects conflicting files and markers
- 02Resolves conflicts with minimal edits
- 03Regenerates lockfiles with package tools
- 04Runs compile, lint, and relevant tests
- 05Summarizes decisions and outcomes
Use cases
- 01Resolving conflicts before a build
- 02Keeping both sides of a conflict when safe
- 03Checking a branch after conflict resolution
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/fix-merge-conflictsin Claude Code to confirm it loaded.
Details
From the project READMEFix merge conflicts
Trigger
Branch has unresolved merge conflicts and needs a reliable path to a buildable state.
Workflow
- Detect all conflicting files from git status and conflict markers.
- Resolve each conflict with minimal, correctness-first edits.
- Prefer preserving both sides when safe. Otherwise, choose the variant that compiles and keeps public behavior stable.
- Regenerate lockfiles with package manager tools instead of hand-editing.
- Run compile, lint, and relevant tests.
- Stage resolved files and summarize key decisions.
Guardrails
- Keep changes minimal and readable.
- Do not leave conflict markers in any file.
- Avoid broad refactors while resolving conflicts.
- Do not push or tag during conflict resolution.
Output
- Files resolved
- Notable resolution choices
- Build/test outcome
Comments
Markdown supported