flokay:wait-ci

Poll GitHub CI check and pull request review statuses for the current branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of waiting for Continuous Integration (CI) checks and pull request reviews to complete, preventing manual status checks and ensuring code quality before merging.

Core Features & Use Cases

  • Automated CI Polling: Continuously checks the status of CI builds for a given pull request.
  • Review Status Monitoring: Identifies blocking reviews (e.g., CHANGES_REQUESTED) and reports them.
  • Log Enrichment: Fetches logs for failed CI runs to aid in debugging.
  • Use Case: After pushing a code change, you can tell your AI assistant to "wait for CI to pass," and it will automatically monitor the progress, notify you of success or failure, and even provide details on why it failed.

Quick Start

Wait for the CI checks on the current pull request to complete.

Frequently Asked Questions about flokay:wait-ci

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

FAQPage Schema
How do I monitor GitHub Actions CI status for a pull request automatically?

You can monitor GitHub Actions CI status automatically by having this Skill poll the current branch's pull request to identify passing, failing, or pending check states and retrieve logs for failed runs.

How does pull request review status checking work for blocking reviews?

Pull request review status checking identifies blocking reviews like CHANGES_REQUESTED and reports unresolved PR comments to prevent merging code that still requires changes.

Can I fetch logs for failed continuous integration runs directly through my AI assistant?

Yes, you can fetch logs for failed continuous integration runs by instructing your AI assistant to wait for CI, which triggers automated polling and log enrichment for failed GitHub Actions builds.

What is the best way to wait for CI checks to pass before merging code changes?

The best way to wait for CI checks to pass is to automate the polling process, which monitors GitHub Actions build progress and notifies you of success or failure along with debugging logs.

Does this CI polling approach work with GitHub Actions and unresolved PR comments?

Yes, this CI polling approach works with GitHub Actions and unresolved PR comments by continuously checking the current branch's pull request for pending states, blocking reviews, and failed build logs.