skills.rest
mvillmow
mvillmowCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gh-batch-merge-by-labels

Batch merge GitHub pull requests by label after verifying CI and approvals.

18|5|Updated Nov 3, 2025
Search Tags:#automation#git#workflow#release management#pull request#github#batch merge
One-click install
npx skills add https://github.com/mvillmow/ProjectOdyssey --skill gh-batch-merge-by-labels
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-batch-merge-by-labels
Source: https://github.com/mvillmow/ProjectOdyssey/tree/main/.claude/skills/gh-batch-merge-by-labels
Command: npx skills add https://github.com/mvillmow/ProjectOdyssey --skill gh-batch-merge-by-labels

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

Manually merging multiple approved pull requests is repetitive, inefficient, and prone to errors, especially during end-of-sprint or release cycles.

Core Features & Use Cases

  • Label-Based Batch Merging: Merges multiple PRs at once based on specific labels (e.g., "ready-to-merge").
  • Merge Options: Supports squash, merge commit, or rebase options for clean Git history.
  • Use Case: At the end of a sprint, use this skill to merge all pull requests labeled "ready-to-merge" that have passed CI and received approvals, streamlining your release process.

Quick Start

Use the gh-batch-merge-by-labels skill to list all open pull requests labeled "ready-to-merge".

Frequently Asked Questions about gh-batch-merge-by-labels

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

FAQPage Schema
How do I merge multiple pull requests at once in GitHub?▼

Batch merge multiple PRs by applying a shared label (e.g., "ready-to-merge") to each, then use gh-batch-merge-by-labels to merge them together. The skill verifies CI status and approvals before merging, reducing manual overhead during sprints or releases.

Can I automate merging approved pull requests by label?▼

Yes. Assign a label to approved PRs, then gh-batch-merge-by-labels automatically merges all labeled PRs that pass CI and approval checks. Supports squash, rebase, or merge commit strategies for clean Git history.

What's the best way to handle end-of-sprint pull request merges?▼

Label all ready PRs with a consistent tag, then batch merge them using gh-batch-merge-by-labels. It checks for conflicts and dependency chains, merging multiple PRs in one operation instead of manually merging each.

Does batch PR merging work with dependent pull requests?▼

Yes. gh-batch-merge-by-labels includes dependency checking, enabling you to merge chains of dependent PRs labeled with the same status. It detects conflicts before merging to prevent integration failures.

What merge strategies does batch merging support?▼

Batch merging supports squash, rebase, and merge commit options. Choose your strategy when running the skill to maintain your repository's Git history standards across all merged PRs.

Do I need GitHub CLI installed to use batch PR merging?▼

Yes. gh-batch-merge-by-labels requires the GitHub CLI (gh) as a dependency. Install it before using the skill to query and merge pull requests.

Related Skills

Explore More Software Engineering Skills→
thimsluggathimslugga

gh-cli

Automate GitHub operations via the gh CLI for repositories, issues, PRs, actions, projects, and releases.

Community
Advanced
rsyslogrsyslog
2.3k

rsyslog_v8stable_patch_flow

Track changelogs, handle pull requests, and merge rsyslog v8-stable patches into main.

Official
Intermediate
gobikomgobikom
2

prp-cleanup

Automate post-merge cleanup by verifying merge status, archiving artifacts, and deleting branches.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

gh-batch-merge-by-labels

Merge GitHub pull requests by labels using the GitHub CLI.

Official
Advanced