agentleFS
developerz-aideveloperz-ai/open-mmorpg/.claude/skills/merge-pr/SKILL.md

merge-pr

Skill17 starsChanged 6 days agoMITView on GitHub

Merge a GitHub PR by looping until it's green and mergeable — waits for CI, fixes failures with the Claude SDK, addresses CodeRabbit review comments, resolves conflicts, then merges. Use when the user asks to merge a PR, land a branch, get a PR green, or clear CI/review comments. Wraps `claudetm merge-pr`.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use implement-issue, create-pr and 2 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.
  • GoogleSkill

    implement-issue

    Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 7 projects that use this

  • sahinSkill

    create-issue

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

  • Other versions18 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 18

    1. ShareX/ShareX★ 41ksame name
    2. cube-js/cube★ 21ksame name
    3. ddnexus/pagy★ 5ksame name
    4. mihai-dinculescu/tapo★ 877same name
    5. bazel-contrib/rules_python★ 692same name
    6. kkokosa/dotLLM★ 528same name
    7. r3bl-org/r3bl-open-core★ 486same name
    8. tbhb/vale-ai-tells★ 118same name
    9. TermiX-official/cryptoclaw★ 100same name
    10. kdy1/kdy1-scripts★ 34same 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After opening a fat, feature-complete PR for a plan batch (workflow).

    line 12
  2. Distinctive:

    Run in the repo. It uses the current branch's PR unless you pass a number/URL.

    line 15
  3. Distinctive:

    Prefer running it in the background (long-running loop) and reporting the outcome:

    line 25
  4. Distinctive:

    Wait for CI checks to report.

    line 32
  5. Distinctive:

    If CI is red → diagnose and fix with the Claude SDK, push.

    line 33
  6. Distinctive:

    If there are review comments (CodeRabbit / reviewers) → address them inline, push.

    line 34
  7. Distinctive:

    If the branch conflicts with base → resolve, push.

    line 35
  8. Distinctive:

    If it exhausts iterations without going green, report the last failing check/comment to the user rather than force-merging.

    line 45
  9. Very specific:

    Check availability with claudetm merge-pr --help.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “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

merge-pr

Land a PR the hands-off way: claudetm merge-pr monitors the PR, fixes CI failures and review comments (CodeRabbit included) with the Claude SDK, resolves merge conflicts, and merges once everything is green — looping until mergeable. This is how big fat PRs land without a human bottleneck.

When to use

  • "merge this PR" / "land my branch" / "get PR 52 green" / "handle the CodeRabbit comments and merge".
  • After opening a fat, feature-complete PR for a plan batch (workflow).

How to run

Run in the repo. It uses the current branch's PR unless you pass a number/URL.

claudetm merge-pr                 # merge the PR for the current branch
claudetm merge-pr 52              # merge PR #52
claudetm merge-pr https://github.com/owner/repo/pull/52
claudetm merge-pr 52 -m 5         # cap at 5 fix iterations (default 30)
claudetm merge-pr 52 --no-merge   # fix + make ready, but don't merge

Prefer running it in the background (long-running loop) and reporting the outcome:

claudetm merge-pr 52

What it does each iteration

  1. Wait for CI checks to report.
  2. If CI is red → diagnose and fix with the Claude SDK, push.
  3. If there are review comments (CodeRabbit / reviewers) → address them inline, push.
  4. If the branch conflicts with base → resolve, push.
  5. Re-check. Merge when green; otherwise loop (until --max-iterations).

Options

  • -m, --max-iterations N — max fix iterations before giving up (default 30).
  • --no-merge — fix and make mergeable, but stop short of merging (use when a human wants the final click).

Notes & guardrails

  • Needs gh auth and push rights to the PR branch.
  • It pushes commits and merges — an outward, hard-to-reverse action. Confirm the target PR with the user first unless they've clearly authorized this run.
  • If it exhausts iterations without going green, report the last failing check/comment to the user rather than force-merging.
  • Check availability with claudetm merge-pr --help.

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.