resolving-merge-conflicts
Skill15 starsChanged 15 days agoMITView on GitHub
Use when you need to resolve an in-progress git merge/rebase conflict.
139 other projects use a version of this, 78 of them edited; 4 new projects in the last 4 weeks, against 2 the 4 before.
Adopted by
Rising: 4 new projects took it in the last 4 weeks, 2× the 4 weeks before.thin data
Most recently taken up by
- The-Vibe-Company/quivrword for word, first seen Nov 8, 2026
- dfirmin/compassedited, first seen Nov 8, 2026
- kazemcodes/skill-treeedited, first seen Nov 8, 2026
- ValorVie/custom-skillsedited, first seen Nov 8, 2026
- Tresnanda/kybernword for word, first seen Nov 8, 2026
- HarryMtv/create-frontstackedited, first seen Nov 8, 2026
Used with
Projects with it also use setup-ts-deep-modules, decision-mapping and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 28 projects that use this
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 5 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 33 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 28 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 32 projects that use this
simo97Skillmigrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Also in 35 projects that use this
Other versions139 projects use a version of this.
Word for word · 43
- QuivrHQ/quivr★ 40k100% same
- The-Vibe-Company/quivr★ 40k100% same
- crbnos/carbon★ 2.8k100% same
- moeru-ai/xsai★ 667100% same
- iamyoki/qwen-image-2.1-skill★ 116100% same
- Dimon94/dverity★ 107100% same
- Dimon94/skills★ 107100% same
- Tresnanda/kybern★ 83100% same
- VoDaiLocz/kilo-kit-mcp★ 28100% same
- JianFeiGan/agent_part★ 17100% same
33 more not listed
Edited · 78
- bestofjs/bestofjs★ 3.1k100% same
- CelestoAI/SmolVM★ 1.2k85% same
- aws/graph-explorer★ 490100% same
- hcloud-talos/terraform-hcloud-talos★ 362100% same
- ninehills/skills★ 280100% same
- loulanyue/skills★ 231100% same
- tt-a1i/matt-skills-with-to-goal★ 19284% same
- HarryMtv/create-frontstack★ 103100% same
- ahonn/dotfiles★ 62100% same
- applypack/applypack★ 3077% same
68 more not listed
Wrote their own version · 18
- nodetool-ai/nodetool★ 615same name
- stevesolun/ctx★ 583same name
- GGGODLIN/gggodlin-cc-harness★ 73same name
- WenWuZhiDao/mattpocock-skills-zh★ 27same name
- axiomantic/spellbook★ 11same name
- imMamdouhaboammar/matts-skills-into-chatgpt★ 8same name
- Boom-Vitt/skills-thai★ 5same name
- dekoza/oh-my-slop★ 4same name
- icetomoyo/CodingSkills★ 4same name
- KroxiDev/engineering-skills★ 4same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository53 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyze-repoSkill
- architectSkill
- codebase-designSkill
- code-reviewSkill
- commitSkill
- create-prSkill
- create-verification-skillSkill
- debugSkill
- frontendSkill
- implementSkill
- mswSkill
- playwrightSkill
- react-hook-form-auditSkill
- react-hook-formSkill
- reactSkill
- refactorSkill
- researchSkill
- specSkill
- tailwindSkill
- tanstack-querySkill
- testSkill
- typescriptSkill
- zodSkill
- auditSkill
- neovimSkill
- shell-envSkill
- teachSkill
- tilSkill
- atomic-note-to-mocSkill
- close-daySkill
- create-noteSkill
- goalsSkill
- import-goodreadsSkill
- import-meetingsSkill
- ingestSkill
- memory-recallSkill
- process-inboxSkill
- projectSkill
- save-sessionSkill
- todays-focusSkill
- vault-auditSkill
- vaultSkill
- weekly-reviewSkill
- careerSkill
- check-communicationSkill
- deslopifySkill
- standupSkill
- blogSkill
- broSkill
- docsSkill
- talkSkill
- tweet-todaySkill
The file
Files
- See the current state of the merge/rebase. Check git history, and the conflicting files.
- 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.
- 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. - Discover the project's automated checks and run them, typically typecheck, then tests, then format. Fix anything the merge broke.
- Finish the merge/rebase. Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

