gh-checks

Diagnose GitHub Actions CI check statuses and failure logs for pull requests.

2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/joegoldin/agent-skills --skill gh-checks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-checks
Source: https://github.com/joegoldin/agent-skills/tree/main/skills/gh-checks
Command: npx skills add https://github.com/joegoldin/agent-skills --skill gh-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of understanding and diagnosing the status of GitHub Actions CI checks for pull requests, reducing the time spent on manual troubleshooting.

Core Features & Use Cases

  • Status Overview: Quickly get an overview of all checks with their status and conclusion.
  • Detailed Check Run Info: Fetch detailed information about each check run, including conclusions and details URLs.
  • Failure Log Reading: Extract and parse failure logs for common issues like test failures, lint failures, and build failures.
  • Annotations: Retrieve annotations and summary errors for a deeper understanding of failures.
  • Multiple PR Handling: Efficiently check the status and logs for multiple pull requests at once.
  • Diagnosing Failures: Provide a summary table, failure details, root cause identification, fix suggestions, and scope notes to help users resolve issues.
  • Re-running Checks: Allow re-running of checks or specific failed jobs for transient failures.

Quick Start

Use the gh-checks skill to fetch and display the status of checks for PR #123 in the 'owner/repo' repository.

Frequently Asked Questions about gh-checks

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

FAQPage Schema
How do I diagnose GitHub Actions CI check failures for pull requests?

To diagnose GitHub Actions CI check failures, you can fetch detailed check run info, parse failure logs for test or build issues, and retrieve annotations to identify root causes for your pull requests.

What is the best way to view GitHub Actions failure logs and annotations for multiple PRs?

Viewing GitHub Actions failure logs and annotations for multiple PRs involves fetching a status overview for each pull request, then extracting summary errors and detailed failure logs to understand the scope of issues.

Do I need the gh command-line tool to check GitHub Actions CI status?

Yes, you need the gh command-line tool installed and GitHub API access to check GitHub Actions CI status and extract failure logs for pull requests using this diagnostic workflow.

Can I re-run failed GitHub Actions checks or specific jobs directly?

You can re-run failed GitHub Actions checks or specific failed jobs directly to resolve transient failures, allowing you to verify fixes without manually triggering the entire pipeline again.

How does parsing CI failure logs help identify root causes and suggest fixes?

Parsing CI failure logs helps identify root causes by extracting common issues like test or lint failures, providing a summary table, scope notes, and fix suggestions to guide troubleshooting.