with one click
merge-pr
Merge a pull request using gh pr merge --admin
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Merge a pull request using gh pr merge --admin
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Approve a pull request using gh pr review --approve
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
Clean up unnecessary local branches and prune stale remote-tracking branches
Clean git worktrees created by git-worktree-runner
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
Analyze the differences between the current branch and origin/main, and summarize the current work progress
| name | merge-pr |
| description | Merge a pull request using gh pr merge --admin |
Merge a pull request using gh pr merge --admin.
$ARGUMENTS
Parse $ARGUMENTS to identify the PR to merge:
123, #123, https://github.com/owner/repo/pull/123gh pr view --json number,title,state
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.
Before merging, confirm the PR details:
gh pr view <pr_number> --json number,title,state,mergeable,author,baseRefName,headRefName
Check:
OPENIf the PR is not open or not mergeable, inform the user and stop.
Verify that all CI checks have passed before merging:
gh pr checks <pr_number>
Check:
pass statuspending or failIf any checks have failed or are still running, inform the user and ask whether to:
--admin will bypass required checks)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.
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.
After merging:
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/import-targets).