github-pr-merge
by fvadicamogithub-pr-merge helps you safely merge GitHub Pull Requests with a lightweight pre-merge check, user confirmation, and post-merge cleanup. Use this github-pr-merge skill when you need a guided github-pr-merge for PR Review workflow, including review-comment checks and milestone awareness before merge.
This skill scores 74/100, which means it is list-worthy but only moderately strong: directory users get a real, triggerable merge workflow with concrete checks, yet should expect some adoption friction because the repository is single-file and lacks supporting references or install guidance.
- Specific merge trigger and scope: it targets merging GitHub PRs after validation, with explicit user intents like merge PR, close PR, and finalize PR.
- Operational workflow is concrete: it includes pre-merge checks such as review comment reply status, milestone checks, and post-merge cleanup.
- Good agent leverage: the body uses shell/gh commands and stop conditions, reducing guesswork compared with a generic prompt.
- No install command, support files, or references, so users have less help understanding setup or trust boundaries before adopting it.
- Marked with an experimental/test signal and the visible excerpt is truncated, so some workflow completeness and edge-case handling are harder to verify.
Overview of github-pr-merge skill
What github-pr-merge does
The github-pr-merge skill helps an agent safely merge a GitHub Pull Request with a lightweight pre-merge check, user confirmation, and post-merge cleanup. It is best for situations where you want more than a bare gh pr merge command but less than a full release process.
Who it is for
Use the github-pr-merge skill when the task is to finalize a PR in an active repo and you want the agent to verify obvious blockers first. It is a good fit for maintainers, repo admins, and agent workflows that need consistent merge behavior across PRs.
What makes it different
The main value of github-pr-merge is its merge gatekeeping: it checks review-comment status, looks for milestone context, and prompts for confirmation before completing the merge. That makes the github-pr-merge for PR Review workflow safer when the repo depends on reviewers closing the loop before merge.
How to Use github-pr-merge skill
Install github-pr-merge
For github-pr-merge install, add the skill with:
npx skills add fvadicamo/dev-agent-skills --skill github-pr-merge
Then confirm the skill folder exists at skills/github-pr-merge and read SKILL.md first. This skill has no helper scripts or reference folders, so the main source of truth is the skill file itself.
What to provide up front
A strong github-pr-merge usage prompt should name the repository, the PR to merge, and any policy constraints that matter. For example, include whether you want squash, merge, or rebase; whether the branch is already approved; and whether you expect milestone or release-note checks.
Good input looks like:
- “Merge PR #184 in
org/repoafter confirming no unreplied review comments and summarize milestone status.” - “Use
github-pr-mergeto finalize the current PR only if CI is green and the author requested squash merge.”
Suggested workflow
Start by asking the agent to identify the current PR, inspect review comments, check milestone state, and then report whether merge conditions are clean. If the checks pass, the skill should ask for confirmation before merging and then handle the cleanup steps after merge.
Files to read first
Read SKILL.md first, then check any repo-local policy files that may override merge behavior, such as AGENTS.md or repository instructions. In this repo, there are no rules/, resources/, or scripts/ directories to expand the workflow, so you should rely on the skill file plus your repository context.
github-pr-merge skill FAQ
Is github-pr-merge only for merging, not reviewing?
Yes. The github-pr-merge skill is focused on the merge decision and execution path, not on writing review feedback. If review comments are still unreplied, the skill is designed to stop and hand off to github-pr-review instead.
When should I not use github-pr-merge?
Do not use it if the PR is still under active review, if unresolved review comments remain, or if your repo needs a custom release or approval chain that the skill does not encode. It is also a poor fit when you need broad policy enforcement beyond the pre-merge checks described in the skill.
Is github-pr-merge beginner friendly?
Yes, if the user can identify the correct PR and answer merge-policy questions. The github-pr-merge guide is simple to run, but results are much better when the user supplies the intended merge method and any repo-specific constraints.
How is this different from a normal prompt?
A generic prompt may merge too early or skip important checks. The github-pr-merge skill adds a repeatable merge sequence, which is especially useful for github-pr-merge for PR Review handoff workflows where the agent must respect review status before merging.
How to Improve github-pr-merge skill
Give the skill the right merge context
The best github-pr-merge skill inputs are specific: PR number, target branch, merge method, and any must-check signals such as milestone, CI status, or reviewer expectations. The more explicit the policy, the less the agent has to guess.
Avoid the common failure modes
The biggest failure mode is trying to merge before comment replies are complete. Another common issue is assuming the milestone state is irrelevant; if your project uses milestones operationally, say so in the prompt and ask the agent to surface that status before merge.
Iterate after the first pass
If the first result is too vague, tighten the prompt with a concrete approval rule, such as “merge only after no unreplied comments, green checks, and explicit confirmation.” If you want a safer github-pr-merge usage pattern, ask for a short pre-merge checklist summary before execution and a one-line post-merge report after completion.