skills.rest
open-horizon-labs
open-horizon-labsOFFICIAL
Explore all skills by this author →
GitHub

oh-merge

Batch-review and merge stacked GitHub PRs in dependency order.

3|Updated Jan 7, 2026
Search Tags:#automation#GitHub#merge#rebase#CI#pull-request#batch-review
One-click install
npx skills add https://github.com/open-horizon-labs/bottle --skill oh-merge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oh-merge
Source: https://github.com/open-horizon-labs/bottle/tree/main/.claude-plugin/plugins/miranda/skills/oh-merge
Command: npx skills add https://github.com/open-horizon-labs/bottle --skill oh-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-review and merge related GitHub PRs into a cohesive, consolidated merge to reduce drift and manual overhead.

Core Features & Use Cases

  • Batch review: Evaluate multiple PRs that address the same feature or issue together to ensure compatibility and avoid conflicting changes.
  • Atomic merges: Merge stacks in dependency order, update child PR bases to main, and rebase as needed to preserve a clean history.
  • CI-aware merging: Verify checks, handle conflicts, and perform squash merges when appropriate.
  • Use Case: When several PRs (e.g., issue/123 with child PRs) must be merged together to deliver a complete feature.

Quick Start

Run the oh-merge command in a repository with PRs labeled oh-merge to start processing stacks.

Frequently Asked Questions about oh-merge

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

FAQPage Schema
How do I batch merge multiple GitHub pull requests into a single commit?▼

Batch merging related GitHub pull requests involves evaluating stacks of PRs that share a base branch, resolving conflicts, and performing squash merges in dependency order to ensure a consolidated, atomic merge.

What is the best way to handle merge conflicts across dependent pull request stacks?▼

Handling merge conflicts across dependent PR stacks requires rebasing the child PRs, updating their base to main, and resolving conflicts systematically before applying atomic merges in dependency order.

How do I merge stacked GitHub pull requests atomically without breaking CI checks?▼

Atomic merges for stacked GitHub pull requests enforce CI checks across the stack, rebase child PR bases to main, and perform squash merges in dependency order to prevent CI failures.

Can I merge related GitHub PRs together if they share the same issue branch?▼

Yes, related GitHub PRs sharing an issue branch can be merged together by batch-reviewing them for compatibility, ordering them by dependency, and executing a cohesive squash merge.

When should I use batch review for stacked pull requests instead of individual merges?▼

Batch review for stacked pull requests should be used when several PRs must merge together to deliver a complete feature, reducing drift and manual overhead compared to individual merges.

Related Skills

Explore More Software Engineering Skills→
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
cookeyholdercookeyholder

squash-pr

Squash and merge a GitHub pull request into main after validating review feedback.

Community
Advanced
nashgaonashgao
3

Merge Pull Request Command

Merge pull requests into a target branch with validation and quality gates.

Community
Advanced
paultyngpaultyng
9

rebase-pr-chain

Rebase stacked GitHub pull requests in dependency order and verify mergeability.

Community
Intermediate