Branch Resolve Conflicts

Name: Branch Resolve Conflicts
Author: risadams

ASecurity

Use when a git merge or rebase hits complex conflicts, or the user says \"resolve conflicts\" / \"fix merge conflicts\". Reconstructs intent, preserves both branches' goals when possible, and runs automated checks.

2 stars
0 votes
0 copies
1 view
Added September 6, 2026

ai-agentsgobashgit

Works with

claude code

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 25, 2026

npx -y skills add risadams/ink-and-agency --skill branch-resolve-conflicts --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Branch Resolve Conflicts?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Branch Resolve Conflicts

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/risadams-branch-resolve-conflicts/badge)](https://www.skillsdirectory.com/skills/risadams-branch-resolve-conflicts)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: branch-resolve-conflicts
category: developer-experience
description: "Use when a git merge or rebase hits complex conflicts, or the user says \"resolve conflicts\" / \"fix merge conflicts\". Reconstructs intent, preserves both branches' goals when possible, and runs automated checks."
codex-short-description: "Resolve complex merge and rebase conflicts, preserving both branches' intent"
argument-hint: "Optional: PR number, ticket, or merge context (e.g., 'GitHub #1234' or 'merging feature/checkout into main')"
version: 1.0.0
license: MIT
allowed-tools:
  - Read
  - Edit
  - Bash
  - Grep
  - Glob
related-skills:
  - branch-rebase
  - codebase-improve-architecture
loop-eligible: false

compatibility: claude-code codex opencode
---
## Workflow

1. **See the current state** of the merge/rebase. Check git history, and the conflicting files.

2. **Find the primary sources** for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues/tickets.

3. **Resolve each hunk.** Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do **not** invent new behaviour. Always resolve; never `--abort`.

4. Discover the project's **automated checks** and run them — typically typecheck, then tests, then format. Fix anything the merge broke.

5. **Finish the merge/rebase.** Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.
---

## See also

- **[README](README.md)** — Full guide with examples and best practices
- **[examples.md](examples.md)** — Annotated conflict resolution walkthroughs

> **Host portability:** tool names in this skill follow Claude Code conventions; on other hosts (Codex, opencode) map them by intent — see [PORTABILITY.md](../PORTABILITY.md).

<!-- self-evolve:start -->
## Self-Evolve Loop
Journal `~/.ink-and-agency/learnings/branch-resolve-conflicts.md` (or workspace-local `.ink-and-agency/` where the sandbox confines writes). Read it first; append what the run taught — [SELF-EVOLVE.md](../SELF-EVOLVE.md).
<!-- self-evolve:end -->