gh-batch-merge-by-labels

Merge GitHub pull requests by labels using the GitHub CLI.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill gh-batch-merge-by-labels-homericintelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-batch-merge-by-labels
Source: https://github.com/HomericIntelligence/ProjectOdyssey/tree/main/.claude/skills/gh-batch-merge-by-labels
Command: npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill gh-batch-merge-by-labels-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of merging multiple GitHub Pull Requests (PRs) simultaneously based on shared labels, significantly reducing manual overhead for release or sprint merges.

Core Features & Use Cases

  • Batch Merging: Merge numerous approved PRs with a single command.
  • Label-Based Selection: Targets PRs tagged with specific labels (e.g., 'ready-to-merge', 'approved').
  • Use Case: At the end of a sprint, you can use this Skill to merge all PRs tagged with 'ready-to-merge' and 'approved', streamlining your release process.

Quick Start

Use the gh-batch-merge-by-labels skill to merge all pull requests labeled 'ready-to-merge' by squashing their commits and deleting the branches.

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 GitHub pull requests at once?

Batch merging multiple GitHub pull requests is automated by this Skill using shared labels to target approved PRs simultaneously. You can merge numerous approved pull requests with a single command based on specified label criteria.

What is the best way to automate sprint release merges on GitHub?

Automating sprint release merges is best handled by targeting PRs tagged with specific labels like 'ready-to-merge' and 'approved'. This streamlines your release process by merging all qualifying PRs in bulk.

Do I need GitHub CLI installed to batch merge pull requests by label?

Yes, GitHub CLI (gh) is required for execution to batch merge pull requests by label. The Skill uses the GitHub CLI to facilitate the bulk merging process while adhering to branch protection rules.

Does batch merging pull requests by label support squash and rebase strategies?

Batch merging pull requests by label supports merge strategies like squash or rebase. The Skill adheres to your configured branch protection rules and merge strategies when processing the selected PRs.

How does label-based selection work for bulk PR merging?

Label-based selection for bulk PR merging works by targeting pull requests tagged with specific shared labels. The Skill scans for PRs matching criteria like 'ready-to-merge' and merges them simultaneously.

Can I delete branches automatically when batch merging labeled pull requests?

Yes, you can delete branches when batch merging labeled pull requests by squashing their commits. The Skill facilitates efficient release management by executing the merge and branch deletion together.