Merge the current branch's PR after confirmation
71%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/pr-merge/SKILL.mdUse this skill when the user asks to run the migrated command pr-merge or invokes $pr-merge.
Merge the GitHub PR for the current branch. This is the ONLY authorized path to merge a PR.
gh pr view --json number,url,title,state,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup \
--jq '{number, url, title, state, mergeable, mergeStateStatus, reviewDecision, checks: [.statusCheckRollup[]? | {name: .name, status: .status, conclusion: .conclusion}]}'If no PR exists, stop: "No open PR found for branch $(git branch --show-current)."
Report any blockers:
If there are blockers, report them and stop. Do not proceed.
Present the PR summary and ask for confirmation:
PR #<number>: <title>
CI: ✅ all passing (or ❌ N failing)
Reviews: ✅ approved (or ⚠️ pending / ❌ changes requested)
Conflicts: none (or ⚠️ has conflicts)
Merge method?Use AskUserQuestion to let the user pick the merge method:
gh pr merge <number> --<method> --delete-branchWhere <method> is squash, rebase, or merge based on the user's choice.
✅ Merged PR #<number> via <method>
<pr_url>
Branch deleted: <branch>git checkout main && git pull --pruneThe --prune flag removes local remote-tracking refs for branches deleted on the remote (including the just-merged branch).
phatblat/dotfiles
4d65cab
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.