wait-for-pr

Wait for GitHub Actions checks and review feedback into a unified readiness summary.

5|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dburkart/auto-engineer --skill wait-for-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wait-for-pr
Source: https://github.com/dburkart/auto-engineer/tree/main/.claude/skills/wait-for-pr
Command: npx skills add https://github.com/dburkart/auto-engineer --skill wait-for-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid guessing whether a pull request is truly ready by consolidating CI status and review-bot feedback into one clear report.

Core Features & Use Cases

  • CI readiness polling: Waits until every GitHub Actions check reaches a terminal state and no action-required approvals are pending.
  • Review aggregation: Detects review-bot comments and formal reviews, with a time-based fallback so you are never blocked forever.
  • Lightweight auto-fix: If a failed check is trivially fixable (format or lint), it applies a single guarded auto-fix and re-waits for results.

Use case: After you create a PR and expect CI plus review feedback to land, invoke this Skill to automatically wait through the full cycle and then deliver one unified status summary.

Quick Start

Tell your assistant: "After I create a PR, run wait-for-pr to monitor CI and review feedback and then return a single consolidated summary."

Frequently Asked Questions about wait-for-pr

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

FAQPage Schema
How do I wait for GitHub pull request CI checks and review bots to finish?▼

To wait for GitHub pull request CI checks and review bots, you can use a polling skill that waits until all GitHub Actions reach a terminal state and captures review feedback into a single readiness summary. It handles PRs with missing review bots using a 30-minute fallback timeout.

Can I automatically fix failed lint or format checks on a pull request?▼

Yes, you can automatically fix failed lint or format checks on a pull request when they are trivially fixable. The process applies a single guarded auto-fix to the failing check and then re-waits for the CI results to reach a terminal state.

What is the best way to consolidate GitHub PR review feedback and CI status?▼

The best way to consolidate GitHub PR review feedback and CI status is to use a monitoring tool that detects review-bot comments and formal reviews, applying a time-based fallback so you are never blocked forever and receive one unified status summary.

How does CI polling handle manual approval blockers on a GitHub pull request?▼

CI polling handles manual approval blockers by detecting action_required statuses on GitHub pull requests. It enforces terminal-state CI gating and ensures no action-required approvals are pending before delivering the final readiness summary.

What happens if review bots are missing on a GitHub pull request?▼

If review bots are missing on a GitHub pull request, the monitoring process enforces a 30-minute bot fallback timeout. This ensures you receive a consolidated status summary without being blocked indefinitely waiting for bot feedback that may never arrive.