How do I install the Merge Pr skill?

Run npx skillmds@latest add dyoshikawa/merge-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Merge Pr skill do?

Merge a pull request using gh pr merge --admin It is listed under Coding & Dev Tools on SkillMD.

Is Merge Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Merge Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Merge Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Merge Pr?

dyoshikawa (@dyoshikawa) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Merge Pr by dyoshikawa — Agent Skill

Name: Merge Pr
Rating: 4.2 (5 reviews)
Author: dyoshikawa

File contents

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

After merging:

Confirm the PR was successfully merged
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:

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).

---name: merge-prdescription: Merge a pull request using gh pr merge --admin---# Merge Pull RequestMerge a pull request using `gh pr merge --admin`.## Input```the user's request```## Step 1: Determine the Target PRParse `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 PRIf 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 PRBefore merging, confirm the PR details:```bashgh 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 confirmationIf the PR is not open or not mergeable, inform the user and stop.## Step 3: Check GitHub Actions Workflow StatusVerify that all CI checks have passed before merging:```bashgh pr checks <pr_number>```Check:1. All workflow checks show `pass` status2. 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 PRExecute the merge command:```bashgh 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 PRAfter the merge succeeds, leave a thank-you comment mentioning the PR author:```bashgh pr comment <pr_number> --body "@<author_login> Thank you!"```Use the `author.login` value obtained in Step 2 for the mention.## Step 6: Report ResultAfter merging:1. Confirm the PR was successfully merged2. Display the merged PR number and title## Step 7: Clean Up Local BranchIf the local branch exists, please clean up the local branch. Execute:```bashgit 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`).

Frequently asked questions

Merge Pr