check-ci

Automates GitHub PR CI checks polling with configurable intervals and timeouts via check_ci.sh script.

47|11|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill check-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-ci
Source: https://github.com/majesticlabs-dev/majestic-marketplace/tree/main/plugins/majestic-engineer/skills/check-ci
Command: npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill check-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates monitoring of GitHub PR CI checks by polling status until success, failure, or timeout.

Core Features & Use Cases

  • Script-based CI polling (check_ci.sh)
  • GitHub CLI integration to fetch PR checks
  • Exit codes to indicate status and provide next steps

Quick Start

Run: ./scripts/check_ci.sh [PR_NUMBER] [INTERVAL] [TIMEOUT]

Frequently Asked Questions about check-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 pass or fail?

Monitoring GitHub PR CI checks automates polling the status of your pull request's continuous integration tests. Use check_ci.sh with your PR number to automatically check at regular intervals until the checks complete, fail, or timeout, returning an exit code indicating the final status.

Can I automate waiting for CI to complete on a GitHub pull request?

Yes. The check_ci.sh script automates CI polling by repeatedly querying your PR's check status through the GitHub CLI at a configurable interval. You set a timeout threshold, and the script returns when checks pass, fail, or time out.

What prerequisites do I need to monitor PR checks with the GitHub CLI?

You need a local git repository, the gh CLI installed and authenticated to GitHub, and the PR number or repository context. The script auto-detects your repository and PR, then uses gh to fetch and poll check statuses.

How do I set the polling interval and timeout for CI checks?

Pass interval and timeout parameters to check_ci.sh when running it: ./scripts/check_ci.sh [PR_NUMBER] [INTERVAL] [TIMEOUT]. The interval controls how often checks are polled, and timeout limits how long the script waits before returning a timeout exit code.

What exit codes does the CI check script return?

The script returns exit code 0 for successful checks, 1 for failed checks, and 2 for timeout. These exit codes let you branch your workflow based on the CI result in CI/CD pipelines or shell scripts.

Does CI check monitoring work across multiple GitHub repositories?

Yes. The script applies to pull requests across GitHub repositories. It auto-detects your repository context from the local git configuration, so you can monitor PRs in any repository where you have gh CLI access.