skills.rest
bravros
bravrosOFFICIAL
Explore all skills by this author →
WebsiteGitHub

batch-merge-prs

Verifies and serially merges multiple GitHub pull requests into a staging branch with per-merge issue closeout.

3|Updated Apr 11, 2026
Search Tags:#code review#git workflow#github#pull requests#issue tracking#batch merge#staging branch
One-click install
npx skills add https://github.com/bravros/bravros --skill batch-merge-prs-bravros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: batch-merge-prs
Source: https://github.com/bravros/bravros/tree/main/plugins/core/skills/batch-merge-prs
Command: npx skills add https://github.com/bravros/bravros --skill batch-merge-prs-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Merging many open pull requests one by one is slow and error-prone: reviews go stale, merge order causes conflicts, linked issues stay open, and a regression can slip into staging. This Skill orchestrates the whole batch so each PR is verified, merged in a safe order, and its linked issue or backlog item is closed. ## Core Features & Use Cases - Parallel pre-merge verification: Runs a read-only review workflow per PR producing clean / needs-changes / superseded / blocked verdicts, with an optional deep mode that checks out each PR and proves net-new tests with a red-green run. - Serial ordered merging: Merges PRs one at a time in ascending order to the staging branch (never main), re-checking mergeability at each step and recovering from conflicts without stranding the batch. - Per-merge closeout and fleet mode: Closes linked GitHub issues and backlog items after each merge, and supports cohorts of autogenerated error-fix PRs via an integration-branch flow with park rules and a Linear sweep. - Use Case: You have 12 reviewed PRs waiting on the homolog staging branch. Invoke the skill to verify all 12 in parallel, fix or park the flagged ones, merge the rest serially, close their issues, and hand the full test suite to the operator. ## Quick Start Ask the agent to run /batch-merge-prs to verify and merge all open pull requests into the staging branch.

Frequently Asked Questions about batch-merge-prs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch merge multiple GitHub pull requests safely?▼

Verify all PRs in parallel with a read-only review workflow, then merge them serially in ascending order to the staging branch using gh pr merge. Re-check mergeability before each merge, since earlier merges invalidate the initial snapshot.

How to verify PRs before merging with GitHub CLI?▼

Use gh pr diff and gh pr view to inspect each PR, fetch the bot review verdict via server-side --jq filtering, and compare the diff against staging HEAD to detect already-landed changes. A deep mode can also check out each PR and run area tests with a red-green proof.

Does this skill ever merge directly to main?▼

No. All merges target the staging branch (homolog by default), and production promotion happens only through the operator's token-gated /promote flow. A blocked verdict is a full stop that hands the PR to a human.

What happens when a merge conflict occurs mid-batch?▼

The conflicting PR is resolved by merging staging into its branch while keeping both siblings' changes, then re-running the touched area's tests. If it cannot be resolved cleanly, the merge is aborted, the tree is left clean, and the PR is parked while the batch continues.

Why are GitHub issues not auto-closed after merging to staging?▼

GitHub keyword auto-close such as 'fixes #N' only fires on the repository's default branch, not on a staging base. The skill closes each linked issue explicitly with gh issue close after the corresponding PR merges.

When should deep verification mode not be used?▼

Deep mode checks out branches and runs tests, so it requires an exclusive working tree with no operator test suite running. On a live tree, use the default read-only review mode and server-side merges only.

Related Skills

Explore More Software Engineering Skills→
11547613341154761334

pr

Create GitHub pull requests from local branches and uncommitted changes.

Community
Basic
kennyolofsson23-netizenkennyolofsson23-netizen

deploy-flow

Deploy code to production via feature-branch, test, staging, PR, and merge workflow.

Community
Advanced
indigoai-usindigoai-us

land-batch

Triage, review, and sequentially merge open PRs with deploy verification.

Official
Advanced
cloudvoyantcloudvoyant

pr-fix

Fetch open pull requests and generate proposed code fixes for unresolved review comments.

Official
Intermediate