skills.rest
Codagent-AI
Codagent-AIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

wait-ci

Poll GitHub CI status and fetch failed run logs for pull requests.

30|1|Updated Feb 18, 2026
Search Tags:#automation#github#code-review#ci#pull-request#pr-comments#ci-polling
One-click install
npx skills add https://github.com/Codagent-AI/agent-skills --skill wait-ci-codagent-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wait-ci
Source: https://github.com/Codagent-AI/agent-skills/tree/main/skills/wait-ci
Command: npx skills add https://github.com/Codagent-AI/agent-skills --skill wait-ci-codagent-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Manually tracking pull request CI status is time-consuming and error-prone, as developers often miss failed check logs, blocking review requests, or unresolved PR comments even when CI reports a green status.

Core Features & Use Cases

  • Automated CI Polling: Repeatedly checks PR CI status at 10-second intervals for up to a configurable maximum wait time, eliminating the need for manual refreshes.
  • Failure Log Retrieval: Automatically fetches and surfaces logs from failed GitHub Actions runs to speed up debugging of broken checks.
  • Blocking Feedback Detection: Identifies CHANGES_REQUESTED reviews and unresolved PR review comments that block merging, even when all CI checks pass.
  • Use Case: After pushing a feature branch for a new user authentication flow, use this skill to automatically wait for CI to finish, get actionable failure logs if checks break, and confirm no blocking review feedback remains before merging.

Quick Start

Use the wait-ci skill to monitor the CI status and surface any blocking issues for your current pull request, waiting up to 15 minutes by default for all checks to complete.

Frequently Asked Questions about wait-ci

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

FAQPage Schema
How do I monitor GitHub pull request CI status automatically?▼

Automated CI polling repeatedly checks GitHub pull request CI status at 10-second intervals up to a configurable maximum wait time, eliminating manual browser refreshes while waiting for builds to complete.

How do I retrieve failed GitHub Actions run logs for a pull request?▼

Failed GitHub Actions run logs are automatically fetched and surfaced during CI polling, providing actionable failure details from broken checks to speed up debugging without manual log navigation.

Can I detect blocking PR review comments and CHANGES_REQUESTED feedback on GitHub?▼

Yes, blocking PR review feedback including CHANGES_REQUESTED reviews and unresolved comments is detected via GraphQL-powered fetching, identifying merge-blocking threads even when all CI checks pass.

Do I need the GitHub CLI installed to poll CI checks and fetch PR comments?▼

Yes, you need the GitHub CLI installed to poll CI checks and fetch PR comments, as bundled Bash scripts depend on it alongside jq for CI status polling, failed run log retrieval, and GraphQL PR review fetching.

What is the default maximum wait time for CI polling on a GitHub pull request?▼

The default maximum wait time for CI polling on a GitHub pull request is 15 minutes, with checks polled every 10 seconds, and silent execution is supported to integrate into automated workflows.

Related Skills

Explore More Software Engineering Skills→
haryelramalhoharyelramalho

gh-address-comments

Aggregate GitHub pull request review comments and threads via GraphQL.

Community
Intermediate
pacaplanpacaplan
30

flokay:wait-ci

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

Community
Advanced
team-attentionteam-attention
282

create-pr

Create GitHub pull requests from the current branch using the GitHub PR API.

Official
Advanced
saif27217saif27217

github

Manage GitHub pull requests and workflow runs via the gh CLI.

Community
Intermediate