resolving-merge-conflicts git:20261011.ef64499A

Immutable. This exact content never changes and is served at /api/v1/blob/8dc40d6c8cf1ed49.

---
name: resolving-merge-conflicts
description: "Use when you need to resolve an in-progress git merge/rebase conflict."
---

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. Continue toward the requested merge or rebase. Do not abort it unless the user requests that change of intent.

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

5. **Finish the requested merge/rebase.** Stage the resolution files while preserving unrelated local changes. Commit the merge or continue the rebase until its commits are resolved, following the user’s requested Git workflow.