drummer

Batch review and merge stacked PRs labeled drummer-merge with CI checks and rebasing.

3|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/open-horizon-labs/bottle --skill drummer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drummer
Source: https://github.com/open-horizon-labs/bottle/tree/main/.claude-plugin/plugins/miranda/skills/drummer
Command: npx skills add https://github.com/open-horizon-labs/bottle --skill drummer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams manage multiple PRs by batch-reviewing and merging them in a coordinated, atomic flow. It prevents drift and ensures related changes are merged together when appropriate.

Core Features & Use Cases

  • Batch review of PRs labeled drummer-merge to evaluate combined changes for coherence.
  • Build dependency graphs to identify stacks and merge order (root → children).
  • Rebase, update bases, and squash-merge PRs in a stack while preserving task closures.
  • Update child PR bases to main after parent merges and signal completion to Miranda.

Quick Start

Use the drummer skill by running /drummer to batch-review and merge PRs labeled drummer-merge.

Frequently Asked Questions about drummer

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

FAQPage Schema
How do I batch-merge stacked PRs to keep related changes coherent?

Batch-merging stacked PRs is automated by the drummer skill, which reviews PRs labeled drummer-merge, builds dependency graphs, and squash-merges them in root-to-child order to prevent drift. It operates across stacks rooted at main and ba/<task-id> branches.

What is the correct merge order for stacked pull requests?

Stacked pull requests require a root-to-children merge order determined by dependency graphs. The drummer skill identifies this order, rebases parent PRs, updates child PR bases to main after parent merges, and preserves task closures for traceability.

How do I rebase and update child PR bases after merging a parent PR?

Rebasing and updating child PR bases after a parent merge is handled automatically by the drummer skill. It squash-merges parent PRs, updates child bases to main, and signals completion to Miranda to maintain coherent branches.

Do I need CI checks to pass before merging stacked PRs?

CI checks are required before merging stacked PRs. The drummer skill evaluates CI status alongside combined changes for coherence, ensuring related branches pass checks before executing rebase, base update, and squash-merge steps.

What tools do I need to automate batch-merge for GitHub stacked branches?

Automating batch-merge for GitHub stacked branches requires access to gh, git, and ba tooling within the target repository environment. These tools enable the drummer skill to execute dependency graphing, rebasing, and task-closure steps.

Why does my stacked PR workflow suffer from branch drift?

Stacked PR workflows suffer from branch drift when related changes are merged independently. The drummer skill prevents this by batch-reviewing combined changes for coherence and merging them in a coordinated, atomic flow.