Skip to content
dumbwaiter-mcp logo

Dumbwaiter MCP: Wait-for-Change

dumbwaiter-mcp

Provider-agnostic wait-for-change skill that uses the Dumbwaiter MCP server to wait on PR events (GitHub first) via wait.start/status/cancel/await, with progress notifications and durable state.

SKILL.md

Full skill instructions

Dumbwaiter MCP: Wait-for-Change

Goal: give Claude a single, stable way to “wait until X happens” on a code host (GitHub now; GitLab next). This skill teaches Claude when and how to use the Dumbwaiter MCP server’s tools.

Prerequisites

  • Server: this repo builds a stdio MCP server (cargo build && target/​debug/​dumbwaiter-mcp).
  • Auth: export GITHUB_TOKEN=… (repo read permissions are sufficient for commit statuses).
  • Persistence (optional): DUMBWAITER_DB to override ./​state/​dumbwaiter.sqlite.
  • Await settings (optional): DUMBWAITER_AWAIT_TTL_SECS (default 900), DUMBWAITER_WATCHER=1 to enable background polling.

When to use this skill

  • You need to pause orchestration until PR checks turn green, a PR is merged, or checks fail.
  • You want durable waits with a wait_id, cancellable and recoverable after restarts.
  • You want progress updates visible to the host via MCP notify_progress.

Tools overview

  • wait.start → returns { wait_id } for a condition on a selector
  • wait.status → returns current state: pending|satisfied|failed|timeout|cancelled|unknown
  • wait.cancel → cancels a pending wait
  • wait.await → polls provider with exponential backoff; emits progress notifications; resolves to terminal state or timeout

Selectors and conditions (GitHub)

  • selector: { "owner": "ORG", "repo": "REPO", "pr": 123 }
  • Supported condition tokens:
    • checks_succeeded — combined status success
    • checks_failed — combined status failure/​error
    • pr_merged — merged flag true
    • pr_approved — at least one approved review
    • changes_requested — an open review with changes requested
    • workflow_completed — at least one completed workflow run
    • comment_received — any new PR comment/​review/​reaction event (see streaming section below)

For comment_received, optional filters refine which events count. If omitted, since defaults to the wait's created_at timestamp so Dumbwaiter streams everything posted after the wait was created.

Happy-path flow

  1. Start wait
    • name: wait.start
    • arguments: { "provider": "github", "selector": {…}, "condition": "checks_succeeded" }
    • capture wait_id
  2. Await
    • name: wait.await
    • arguments: { "wait_id": "…" }
    • Observe progress notifications; handle final result
  3. Query or cancel as needed
    • wait.status or wait.cancel

Guidelines

  • Prefer wait.await when a host can display progress; otherwise poll with wait.status on an interval < backoff cap (default 30s).
  • Always report final state back to the orchestrator and link the wait_id in logs/​notes.
  • On auth errors or rate limits, surface a clear, actionable message; do not retry aggressively (respect backoff).
  • On timeouts, return timeout with elapsed seconds; let the caller decide next steps.
  • Security: never echo tokens; require least scopes.

Streaming GitHub comment events

Set condition to comment_received plus optional filters:

{
  "provider": "github",
  "selector": { "owner": "acme", "repo": "widgets", "pr": 42 },
  "condition": "comment_received",
  "filters": {
    "since": "2025-01-01T00:00:00Z",
    "include_bots": true,
    "author_allowlist": ["alice"],
    "author_denylist": ["bot"]
  }
}

wait.await emits notify_progress for every matching comment/​review/​reaction (body + URL + reaction counts + code context) before returning the terminal payload that mirrors the streamed events. Use this when an orchestrator needs to react to each individual discussion event.

Examples

  • “Wait for PR 42 in acme/​widgets until checks pass.”
    • start → { provider: "github", selector: { owner: "acme", repo: "widgets", pr: 42 }, condition: "checks_succeeded" }
    • await → { wait_id }
  • “Stream every new comment on PR 42 since midnight UTC.”
    • start → { provider: "github", selector: { owner: "acme", repo: "widgets", pr: 42 }, condition: "comment_received", filters: { since: "2025-01-01T00:00:00Z", include_bots: true } }
    • await → receives per-comment progress events plus the final summary payload

Troubleshooting

  • unknown status: the wait_id was not found (DB purge or wrong project).
  • No progress events: confirm host supports MCP notifications and server is connected.
  • Auth failures: ensure GITHUB_TOKEN is set and valid for the target repo.

More skills from majiayu000

xiaohongshu logo
majiayu000/claude-arsenal

xiaohongshu

xiaohongshu

286 148
View
agent-task-conductor logo
majiayu000/claude-skill-registry

agent-task-conductor

Conduct multi-agent task orchestration and workflow coordination.

663 1
View
conductor-setup logo
majiayu000/claude-skill-registry

conductor-setup

Initialize project with Conductor artifacts (product definition,

663 1
View
animation-designer logo
majiayu000/claude-skill-registry

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS

663 1
View
diagramming logo
majiayu000/claude-skill-registry

diagramming

Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...

663 1
View
h3-pg logo
majiayu000/claude-skill-registry-data

h3-pg

PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.

23 1
View
conductor-development logo
majiayu000/claude-skill-registry

conductor-development

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...

663 1
View
conductor-status logo
majiayu000/claude-skill-registry

conductor-status

Display project status, active tracks, and next actions

663 1
View
dockerization logo
majiayu000/claude-skill-registry

dockerization

Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.

663 1
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View