Agent skill

Merge PR

by dyoshikawa in dyoshikawa/rulesync

Merge a pull request using gh pr merge --admin. An agent skill from dyoshikawa/rulesync.

MITAuto-check passedDevelopment

Install Merge PR

skills CLI
$ npx skills add dyoshikawa/rulesync --skill merge-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dyoshikawa/rulesync merge-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/merge-pr .claude/skills/merge-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
merge-pr
GitHub stars
1.5k
Token cost
~645 tokens
SKILL.md length
338 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Merge a pull request using gh pr merge --admin. An agent skill from dyoshikawa/rulesync.

  • Works in 7 steps: Determine the Target PR → Verify the PR → Check GitHub Actions Workflow Status → …
  • Tasks that involve Pull requests
  • SKILL.md covers Input, Step 1: Determine the Target PR, Step 2: Verify the PR and Step 3: Check GitHub Actions…, plus 4 more sections
  • Calls gh and git; reaches github.com

What it does

Merge PR is an agent skill from dyoshikawa/rulesync. Merge a pull request using gh pr merge --admin

Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/merge-pr”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Determine the Target PR
  2. Verify the PR
  3. Check GitHub Actions Workflow Status
  4. Merge the PR
  5. Comment on the PR
  6. Report Result
  7. Clean Up Local Branch

What it can do on your machine

Read from SKILL.md and the folder at commit 625bf98. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Merge PR loads about 645 tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 338 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~14
When it runs · the whole SKILL.md, loaded when a task matches
~645

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dyoshikawa/rulesync at commit 625bf98, republished under its MIT licence (© dyoshikawa). 338 words, ~645 tokens.

Download SKILL.mdSave it as .claude/skills/merge-pr/SKILL.md (or your agent's skills folder).
name
merge-pr
description
Merge a pull request using gh pr merge --admin
targets
*

Merge Pull Request

Merge a pull request using gh pr merge --admin.

Input

the user's request

Step 1: Determine the Target PR

Parse the user's request to identify the PR to merge:

Case A: PR number or URL is provided
  • Extract the PR number from the argument
  • Examples: 123, #123, https://github.com/owner/repo/pull/123
Case B: No argument provided
  • Get the PR associated with the current branch:
    bash
    gh pr view --json number,title,state
Case C: Unable to determine the PR

If the PR cannot be determined (e.g., no PR exists for the current branch, or the argument is ambiguous), ask the user to specify which PR to merge.

Step 2: Verify the PR

Before merging, confirm the PR details:

bash
gh pr view <pr_number> --json number,title,state,mergeable,author,baseRefName,headRefName

Check:

  1. The PR state is OPEN
  2. Display the PR title and number to the user (for visibility; do not wait for a reply)

If the PR is not open or not mergeable, inform the user and stop.

Step 3: Check GitHub Actions Workflow Status

Verify that all CI checks have passed before merging:

bash
gh pr checks <pr_number>

Check:

  1. All workflow checks show pass status
  2. No checks are pending or fail

If checks are still running, do not ask — wait for them with gh pr checks <pr_number> --watch and merge once they all pass.

If any check has failed, inform the user and ask whether to:

  • Investigate failed checks before merging
  • Proceed with merge anyway (using --admin will bypass required checks)

Step 4: Merge the PR

Execute the merge command:

bash
gh pr merge <pr_number> --admin --merge

Important: Only merge ONE PR at a time. If multiple PRs are somehow specified, ask the user which single PR to merge.

Step 5: Comment on the PR

After the merge succeeds, leave a thank-you comment mentioning the PR author:

bash
gh pr comment <pr_number> --body "@<author_login> Thank you!"

Use the author.login value obtained in Step 2 for the mention.

Step 6: Report Result

After merging:

  1. Confirm the PR was successfully merged
  2. Display the merged PR number and title

Step 7: Clean Up Local Branch

If the local branch exists, please clean up the local branch. Execute:

bash
git checkout main && git pull --prune && git branch -d <branch-name>

Where <branch-name> is the head branch name from Step 2 (e.g., fix/rulesync-import-targets).

© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .rulesync/skills/merge-pr of dyoshikawa/rulesync.

Open the folder on GitHubat commit 625bf98

Compare with similar skills

Merge PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Merge PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Merge PR this skilldyoshikawa/rulesync1.5k—~645Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check passed

More from dyoshikawa/rulesync

All 40 skills in this repo
  • Rulesync Feature Research

    dyoshikawa/rulesync

    Maps rulesync feature implementations to upstream coding-agent documentation.

    1.5k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Babysit Dependabot PR

    dyoshikawa/rulesync

    Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…

    1.5k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Commit Push PR

    dyoshikawa/rulesync

    Commit current changes, push to remote, and create or update a pull request.

    1.5k GitHub stars~458 tokensUpdated yesterday
    Auto-check passed
  • Git Worktree Runner

    dyoshikawa/rulesync

    Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.

    1.5k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check: notes
  • Goal PR

    dyoshikawa/rulesync

    Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.

    1.5k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Goal Release

    dyoshikawa/rulesync

    Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…

    1.5k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Merge PR

What does Merge PR do?

Merge a pull request using gh pr merge --admin. An agent skill from dyoshikawa/rulesync. Merge PR is an agent skill from dyoshikawa/rulesync.

When should I use Merge PR?

Merge PR fits situations like: tasks that involve Pull requests.

How do I install Merge PR in Claude Code?

Run `npx skills add dyoshikawa/rulesync --skill merge-pr -a claude-code`. Or copy the skill folder (.rulesync/skills/merge-pr in dyoshikawa/rulesync) into .claude/skills/merge-pr in your project. Claude Code loads it when a task matches its description.

How do I install Merge PR in Codex?

Run `npx skills add dyoshikawa/rulesync --skill merge-pr -a codex`. Or copy the skill folder (.rulesync/skills/merge-pr in dyoshikawa/rulesync) into .agents/skills/merge-pr in your project. Codex loads it when a task matches its description.

Can I use Merge PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill merge-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/merge-pr, .gemini/skills/merge-pr, .github/skills/merge-pr and .opencode/skills/merge-pr in your project.

What does Merge PR need to run?

Going by SKILL.md and its folder, Merge PR needs the command-line tools its instructions call (gh and git).

Does Merge PR access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Merge PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Merge PR use?

Merge PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Merge PR use?

About 645 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Merge PR?

Skills that share tags, products or a category with Merge PR: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Merge PR?

dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,509 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 9, 2026.

Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.