await-ci

Polls GitHub PR CI checks until they pass, fail, or timeout, then reports the result.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rnwolfe/engram --skill await-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: await-ci
Source: https://github.com/rnwolfe/engram/tree/main/.claude/skills/await-ci
Command: npx skills add https://github.com/rnwolfe/engram --skill await-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Polls a pull request's CI status until all required checks pass, any required check fails, or the timeout is reached. Reports the result clearly so the caller (human or /forge-loop) can decide what to do next.

Core Features & Use Cases

  • Monitor GitHub PR checks and determine when CI has settled.
  • Handle timeouts and report a concise status summary.
  • Provide progress updates during polling and a final success or failure report.

Quick Start

Provide the PR number to begin monitoring CI checks and wait for a settled result.

Frequently Asked Questions about await-ci

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

FAQPage Schema
How do I monitor GitHub PR CI checks until they finish?

To monitor GitHub PR CI checks until they finish, you can poll the pull request status repeatedly to wait for all required checks to pass, fail, or hit a timeout, providing progress updates and a final verdict.

What happens when a required CI check on a pull request fails or times out?

When a required CI check fails or times out, the polling stops immediately and reports a concise failure status summary so the caller can decide the next action without waiting indefinitely.

Can I configure the polling interval and timeout for GitHub CI status checks?

Yes, you can configure both the poll interval and timeout duration for GitHub CI status checks, allowing you to control how frequently the PR checks are queried and the maximum wait time before settling.

Does this work with automated pull request workflows requiring CI settlement?

Yes, it applies to GitHub PR workflows in software projects requiring automated CI settlement, handling multiple CI states and producing clear success or failure outputs for either human or automated callers.

What is the best way to wait for CI to settle on a GitHub pull request?

The best way to wait for CI to settle on a GitHub pull request is to use automated polling that tracks all required checks, provides visible progress during the wait, and reports a clear final result.