From merge-pr
Use when a pull request is ready to merge — verifies CI and review status, syncs with the base branch, confirms with the user, then squash merges and cleans up. Trigger when the user says "merge this", "merge this PR", "squash merge", or "merge it". Works on any open PR — does not require /open-pr to have created it. If no PR exists, redirects to /open-pr. Does NOT deploy to any environment.
How this skill is triggered — by the user, by Claude, or both
Slash command
/merge-pr:merge-prThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Takes a ready PR and lands it: verify → sync → confirm → squash merge → cleanup.
Takes a ready PR and lands it: verify → sync → confirm → squash merge → cleanup.
Announce at start: "I'm using the merge-pr skill to merge this PR."
Check for an open PR on the current branch, or use a user-specified PR number:
# Current branch
gh pr view --json number,title,url,state,baseRefName,headRefName 2>/dev/null
# Or if user specified #N:
gh pr view <N> --json number,title,url,state,baseRefName,headRefName
No PR found: Stop and redirect:
"No open PR found on this branch. Use
/open-prto create one first."
PR found: Note the PR number, title, base branch, and URL. Continue.
Check CI status and review state:
gh pr checks <N>
gh pr view <N> --json reviews --jq '.reviews[] | select(.state == "CHANGES_REQUESTED")'
CI failing: Stop and report which checks are failing. Do not merge.
"CI is failing on [check names]. Fix these before merging, or use
/open-prto address them."
CHANGES_REQUESTED review: Stop and report who requested changes.
"PR has CHANGES_REQUESTED from [reviewer]. Resolve this before merging."
All clear: Continue.
Check whether the base branch has moved since branching:
BASE=$(gh pr view <N> --json baseRefName --jq '.baseRefName')
git fetch origin $BASE
git log HEAD..origin/$BASE --oneline
New commits exist: Rebase and force-push:
git rebase origin/$BASE
git push --force-with-lease
If rebase has conflicts, resolve them, then git rebase --continue. After force-push, re-verify CI passes before continuing.
No new commits: Skip.
Before merging, confirm:
Ready to squash merge PR #<N> ("<title>") into <base>.
All checks passed. Proceed?
Wait for confirmation. If the user says to always proceed without asking (e.g. "auto-merge", "no need to confirm"), skip this prompt for the rest of the session.
Once confirmed:
gh pr merge <N> --squash --delete-branch
After merge, sync locally:
git checkout $BASE
git pull
git branch -d <feature-branch> 2>/dev/null || true
Report: "PR # merged. Branch cleaned up. Done."
| Step | Action | Block on failure? |
|---|---|---|
| 1. Identify PR | Current branch or #N | Yes — redirect to /open-pr |
| 2. Verify readiness | CI + review state | Yes — fix first |
| 3. Base sync | Rebase if behind | Yes — resolve conflicts |
| 4. Confirm | Wait for user | Yes — wait |
| 5. Squash merge | gh pr merge --squash + cleanup | — |
Never:
Always:
/open-prnpx claudepluginhub harnessprotocol/harness-kit --plugin merge-prMerges reviewed PRs when triggered by /pr-merge or merge commands. Handles squash/rebase, worktrees, integration branches, and auto-merge for CI gating.
Verifies CI status, local tests, and repo safety before merging a PR, with post-merge health monitoring. Use when landing a completed implementation.
Drives existing GitHub/GitLab PRs/MRs to merge: monitors CI/CD status, fixes issues in PR scope via sub-skills, handles multi-round code reviews, resolves comments until all requirements met.