agentleFS
koomaikoomai/claude-kit/skills/merge-from/SKILL.md

merge-from

Skill4 starsChanged 16 days agoMITView on GitHub

Merge the target branch into this one, resolving conflicts while preserving this branch's intent. Defaults to the repo's default branch.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify: run the project's test suite if one exists.

    line 21
  2. Distinctive:

    If divergence is severe enough that cherry-picking this branch's intent onto a fresh branch from the target would be cleaner, say so and …

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Task

Target branch: $ARGUMENTS — if blank, detect the repo's default branch via git symbolic-ref refs/remotes/origin/HEAD (fall back to checking for main, then master).

Reconcile this feature branch with the target so it merges cleanly. Never modify the target branch, and never push — leave that to me. If the working tree is dirty, stop and ask before doing anything.

  1. git fetch origin.
  2. Assess the divergence in both directions against origin/<target> — and more importantly, understand the intent of this branch's changes.
  3. Merge origin/<target> into this branch (merge the remote-tracking ref, not a stale local one).
  4. Resolve conflicts: take the target's newer changes by default, but this branch's intent wins where they collide. Example: target modified component.tsx, but this branch renamed it to component-tab.tsx — the rename was intentional, so apply the target's edit to component-tab.tsx and delete component.tsx.
  5. Verify: run the project's test suite if one exists; otherwise build/typecheck. Report anything you couldn't verify.

Done means: no conflicts with the target, no target-branch changes overridden except where this branch's feature required it, and the feature's behaviour intact.

If divergence is severe enough that cherry-picking this branch's intent onto a fresh branch from the target would be cleaner, say so and ask before taking that path.

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.