A procedure for merging a GitHub pull request, which is a proposed set of code changes, with administrator approval. It first identifies the request and checks its state, review details, and automated checks.

It is for finding the pull request linked to a branch, verifying that it is open and mergeable, checking CI results, and completing an administrator merge.

It reduces the risk of merging the wrong request or merging code before required checks and approvals are complete.

merge-pr — Skill for Claude Code and Codex by dyoshikawa: A procedure for merging a GitHub pull request, which…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/dyoshikawa/rulesync/merge-pr

Any agent

npx skills add dyoshikawa/rulesync --skill merge-pr

Clone the repo

git clone --depth 1 https://github.com/dyoshikawa/rulesync

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dyoshikawa/rulesync/merge-pr.svg)](https://agentmods.dev/skills/dyoshikawa/rulesync/merge-pr)

Your own site

<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/merge-pr"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/merge-pr.svg" alt="Measured on agentmods" height="20"></a>

Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 630 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00630
Opus 5	$0.00006	$0.00315
Sonnet 5	$0.00003	$0.00126
Haiku 4.5	$0.00001	$0.00063

Measured 4d ago against content hash 3702d9b84b0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

merge-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.rulesync/skills/merge-pr/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:
```
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:

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

Check:

The PR state is OPEN
Display the PR title and number to the user for confirmation

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:

gh pr checks <pr_number>

Check:

All workflow checks show pass status
No checks are pending or fail

If any checks have failed or are still running, inform the user and ask whether to:

Wait for pending checks to complete
Investigate failed checks before merging
Proceed with merge anyway (using --admin will bypass required checks)

Step 4: Merge the PR

Execute the merge command:

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:

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

Read the full file on GitHub · 108 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago First seen · 108 lines · 13 tokens per session scan A 3702d9b84b0d

Subscribe to this mod's changes

merge-pr is a skill published in the GitHub repository dyoshikawa/rulesync (1,379 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 630 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow LLM ai ai-agents ai-coding mcp rules

deep-clean

Full-spectrum consolidation of AI agent configuration files. Goes beyond memory-only dream skills: audits and optimizes context files (AGENTS.md/AGENTS.md/GEMINI.md/.cursorrules), rules, skills, and memory. Detects stale references, dead file paths, duplicated rules, stack mismatches, contradictions, vague directives…

opencue/cuecards · 87 tokens

turborepo

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines…

Bosh-Kuo/awesome-agent-toolkit · 111 tokens

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for…

Bosh-Kuo/awesome-agent-toolkit · 90 tokens

skill-creator-anthropic

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Bosh-Kuo/awesome-agent-toolkit · 48 tokens

skill-creator-openai

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.