ci-status

Name: ci-status
Availability: InStock
Author: Mifune

Retrieve and report GitHub Actions CI status for the active branch.

28|3|Updated Mar 27, 2026

Search Tags:#automation #workflow #github #pr #ci #checks

Ready to run

npx skills add https://github.com/mifunedev/openharness --skill ci-status-mifunedev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-status
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/ci-status
Command: npx skills add https://github.com/mifunedev/openharness --skill ci-status-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitor the GitHub Actions CI pipeline for the current branch and report PASS/FAIL with failure details after pushes or commits, so you know when code is truly ready.

Core Features & Use Cases

PR-check aware: If an open PR exists for the current branch, fetch and report its checks directly.
Branch-run fallback: When no PR checks are available, query the latest GitHub Actions workflow run for the branch.
Progress polling & results: Poll for completion with a timeout and present the final status, including a link to the run.
Failure context: Retrieve failing job details and logs to diagnose issues quickly.
Decision-ready output: Return a concise PASS/FAIL result with actionable information.

Quick Start

Run ci-status after pushing changes to verify the latest CI status for the active branch.

Frequently Asked Questions about ci-status

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

FAQPage Schema

How do I check GitHub Actions CI status for a branch after pushing code?▼

To check CI status, this Skill automates retrieval of GitHub Actions workflow runs for the active branch, polls for completion, and reports PASS or FAIL with a direct link to the run.

Does this tool report CI checks for open pull requests differently than branch runs?▼

Yes, PR checks are prioritized. When an open PR exists, it fetches PR checks directly; when no PR checks are available, it falls back to the latest branch workflow run for status reporting.

How do I get failing job logs from GitHub Actions to debug a CI pipeline?▼

The Skill retrieves failing job details and logs from GitHub Actions to debug a CI pipeline. It exposes the run status, head SHA, and URL through the gh CLI and GitHub API to enable fast diagnosis.

Can I automate GitHub Actions workflow status polling with a timeout?▼

Yes, the Skill automates GitHub Actions workflow status polling with a timeout. It polls for completion within a defined period and presents the final PASS or FAIL status, including a link to the run.

What is the best way to verify if code is ready after a push to GitHub?▼

The best way to verify code readiness after a push is to monitor the GitHub Actions CI pipeline. This Skill returns a concise PASS or FAIL decision-ready output with actionable information and failure context.

Why does my CI status check fail to find the latest workflow run for my branch?▼

If an open PR exists, the system prioritizes fetching PR checks instead of the latest branch workflow run. When no PR checks are available, it falls back to querying the latest branch workflow run via the GitHub API.