wait-for-ci

Block until GitHub Actions CI checks pass or fail on the current PR.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/pulsemcp/agentic-engineering --skill wait-for-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wait-for-ci
Source: https://github.com/pulsemcp/agentic-engineering/tree/main/skills/wait-for-ci
Command: npx skills add https://github.com/pulsemcp/agentic-engineering --skill wait-for-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wait for GitHub Actions CI checks to finish on the current pull request, ensuring you only proceed when status is green or handle failures gracefully.

Core Features & Use Cases

  • Blocks until all CI checks complete for the PR.
  • Exits 0 when all checks pass, exits non-zero and stops early on failure.
  • Integrates into your development workflow to gate merges and deployments.

Quick Start

Run the gh pr checks --watch --fail-fast to wait for CI and act on the result.

Frequently Asked Questions about wait-for-ci

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

FAQPage Schema
How do I block my workflow until GitHub PR checks finish?

You can block until GitHub PR checks finish by running a watch command that waits for all CI statuses to complete. It stays active until the checks pass or fail, gating your workflow from proceeding prematurely.

What happens when a CI check fails on my pull request?

When a CI check fails on your pull request, the process exits with a non-zero code and stops early using fail-fast behavior. This prevents downstream merge or deployment steps from running on broken code.

Do I need the GitHub CLI to wait for CI checks?

Yes, you need the GitHub CLI installed and authenticated to wait for CI checks. The process verifies these prerequisites and requires you to be on a branch with an open PR before starting.

Can I automate gating merges based on GitHub Actions status?

You can automate gating merges based on GitHub Actions status by integrating this wait step into your workflow. It returns an exit code based on the CI result, allowing scripts to conditionally proceed with merging.

Why does my PR wait command stop early before all checks complete?

Your PR wait command stops early because of the implemented fail-fast behavior. It is designed to exit immediately and return a non-zero status as soon as it detects the first failed CI check.

What is the best way to monitor GitHub Actions CI status for a PR?

The best way to monitor GitHub Actions CI status for a PR is using a watch mode that continuously polls the checks. It blocks your terminal until completion, providing an exit code that reflects the final pass or fail state.