dumbwaiter-mcp

Wait for GitHub PR conditions using the Dumbwaiter MCP server.

2|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/lambdamechanic/sk --skill dumbwaiter-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dumbwaiter-mcp
Source: https://github.com/lambdamechanic/sk/tree/main/skills/dumbwaiter-mcp
Command: npx skills add https://github.com/lambdamechanic/sk --skill dumbwaiter-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need for manual polling and constant monitoring of GitHub Pull Request events, allowing AI agents to pause orchestration and react only when specific conditions are met. It ensures durable, observable, and efficient waiting for changes.

Core Features & Use Cases

  • Event-Driven Waits: Allows AI agents to wait for specific GitHub PR conditions like checks_succeeded, pr_merged, pr_approved, or comment_received.
  • Durable State: Waits are persistent and recoverable across process restarts, identified by a unique wait_id.
  • Progress Notifications: Streams real-time updates on PR activity, including check statuses, workflow runs, and comments, enabling dynamic AI responses.
  • Use Case: An AI agent has submitted a pull request and needs to wait for all CI checks to pass before merging or requesting a review. This skill enables the agent to initiate a wait, receive progress updates, and automatically proceed once the checks are green.

Quick Start

Start a wait for PR #123 in the acme/widgets repository until all checks succeed, and provide the wait_id.

Frequently Asked Questions about dumbwaiter-mcp

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

FAQPage Schema
How do I pause orchestration and wait for GitHub PR checks to pass?

Waiting for PR checks is pausing orchestration until specific GitHub conditions are met. Start a wait with a selector like `checks_succeeded`, receive a durable `wait_id`, and poll status or await completion. The Skill handles polling, persistence, and streaming progress updates automatically.

Can I wait for multiple GitHub PR events like merges, approvals, or comments?

Yes. The Skill supports multiple selector-based conditions: `checks_succeeded`, `pr_merged`, `pr_approved`, `changes_requested`, `workflow_completed`, and `comment_received`. Each wait targets one condition per PR and is identified by a unique `wait_id` for recovery across restarts.

What happens if my process restarts while waiting for a PR event?

Waits are durable and persist in SQLite (default `./state/dumbwaiter.sqlite`). Query the wait status using your stored `wait_id` to resume without losing progress. The Skill recovers state automatically and continues polling from where it left off.

How do I automate CI/CD workflows that depend on PR status checks?

Initiate a wait for a PR condition (`checks_succeeded`, `pr_merged`, etc.), receive real-time progress updates and streaming notifications, then proceed once the condition is met. This eliminates manual polling and enables event-driven automation in orchestration pipelines.

Can I cancel a wait before the GitHub condition is met?

Yes. The Skill implements a `wait.cancel` operation that allows you to terminate an active wait using its `wait_id`. Cancellable waits give you control over long-running orchestration and reduce resource consumption.

Does this work with GitHub Enterprise or only GitHub.com?

The metadata specifies GitHub as the provider but does not document GitHub Enterprise compatibility. Refer to the Skill's configuration documentation or contact the author for platform scope details.