resolving-merge-conflicts

Resolves in-progress git merge and rebase conflicts while preserving both change intents.

1|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/taxmaxi/taxmaxi --skill resolving-merge-conflicts-taxmaxi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolving-merge-conflicts
Source: https://github.com/taxmaxi/taxmaxi/tree/main/.agents/skills/resolving-merge-conflicts
Command: npx skills add https://github.com/taxmaxi/taxmaxi --skill resolving-merge-conflicts-taxmaxi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge and rebase conflicts interrupt development and are often resolved hastily, losing the intent of one side or introducing broken code. This Skill provides a disciplined workflow for understanding each conflict's origin, resolving every hunk correctly, and verifying the result with the project's automated checks. ## Core Features & Use Cases - Conflict Investigation: Inspects git history, commit messages, PRs, and original issues to understand why each conflicting change was made. - Intent-Preserving Resolution: Resolves each hunk by preserving both intents where possible, and documents trade-offs when they are incompatible. - Verification and Completion: Runs the project's typecheck, tests, and formatting, then stages, commits, and continues the rebase until finished. - Use Case: You run git rebase main on a long-lived feature branch and hit conflicts across several files. The Skill traces each change back to its PR, resolves the hunks without inventing new behavior, runs the test suite, and completes the rebase. ## Quick Start Resolve the current git merge conflict in this repository, run the project checks, and finish the merge.

Frequently Asked Questions about resolving-merge-conflicts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve git merge conflicts step by step?▼

First inspect the merge state and conflicting files, then trace each change to its commit, PR, or issue to understand intent. Resolve each hunk preserving both intents where possible, run the project's typecheck and tests, then stage and commit to finish the merge.

How to resolve conflicts during a git rebase?▼

During a rebase, resolve each conflicted hunk based on the original intent of both changes, then stage the files and continue the rebase. Repeat for every commit until all commits are rebased, and run the project's automated checks before finishing.

Should I use git merge or git rebase for resolving branch conflicts?▼

Both produce conflicts that are resolved the same way: understand each change's intent and resolve hunks accordingly. The Skill supports both in-progress merges and rebases, continuing the rebase process until all commits are applied.

When should I abort a merge instead of resolving conflicts?▼

This workflow never aborts; it always resolves the conflict. Aborting discards progress, so instead each hunk is resolved by matching the merge's stated goal, with trade-offs noted when the two intents are incompatible.

Why do merge conflicts keep breaking tests after resolution?▼

Conflicts resolved without understanding both changes often combine incompatible logic. After resolving, run the project's automated checks in order, typically typecheck, then tests, then formatting, and fix anything the merge broke before committing.