agentleFS
Sign inStart free
mdiri-aimdiri-ai/SoduWork/skills/resolving-merge-conflicts/SKILL.md

resolving-merge-conflicts

Skill930 starsChanged 6 days agoMITView on GitHub

Use when you need to resolve an in-progress git merge/rebase conflict.

140 other projects use a version of this, 121 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, decision-mapping and 9 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.
  • liufeng1976Skill

    setup-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

  • FabienDehopreSkill

    decision-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

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 33 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 28 projects that use this

  • LesaniSkill

    writing-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

  • simo97Skill

    migrate-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

The file

Create a free account to mount
Files
SKILL.md

SoduWork runtime: follow the user's authorized scope and repository instructions. This method grants no additional tool, network, credential, or publishing permissions. Use the tools actually available in the selected runtime. If sub-agent tools are unavailable, perform the independent passes sequentially and report that limitation; do not claim parallel execution.

  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 resolving within the user's authorized goal; if the user asks to stop or abort, preserve their work and follow that instruction.
  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. Review the resolved diff, stage only the files belonging to this operation, and follow the repository's commit requirements. Preserve unrelated user changes. If rebasing, continue the already-authorized rebase until all commits are resolved. Do not push, rewrite published history, or update a protected branch without the user's authorization.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free