gh-check-ci-status

Check GitHub pull request CI/CD status and workflow runs via gh CLI.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill gh-check-ci-status-homericintelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-check-ci-status
Source: https://github.com/HomericIntelligence/ProjectOdyssey/tree/main/.claude/skills/gh-check-ci-status
Command: npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill gh-check-ci-status-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the verification of Continuous Integration and Continuous Deployment (CI/CD) status for pull requests, helping to ensure code quality and prevent merge conflicts.

Core Features & Use Cases

  • CI Status Check: Verifies if all automated checks (tests, linting, builds) for a pull request are passing.
  • Failure Investigation: Provides tools to view detailed logs and identify the root cause of CI failures.
  • Use Case: Before merging a pull request, use this Skill to confirm that all CI checks have passed, ensuring the new code doesn't break the build or introduce regressions.

Quick Start

Use the gh-check-ci-status skill to check the CI status of pull request number 123.

Frequently Asked Questions about gh-check-ci-status

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

FAQPage Schema
How do I check the CI/CD status of a GitHub pull request?

You can check CI/CD status by using this Skill to retrieve GitHub pull request workflow runs and test results via the GitHub CLI. It verifies if automated checks including tests, linting, and builds are currently passing.

What is the best way to investigate CI failures in a GitHub pull request?

The best way to investigate CI failures is using this Skill to view detailed logs and identify the root cause. It interacts with the GitHub API to retrieve specific check statuses and workflow run logs for failing PRs.

Do I need the GitHub CLI installed to verify PR checks?

Yes, you need the GitHub CLI (`gh`) installed to verify PR checks. This Skill requires `gh` to interact with GitHub's API for retrieving check statuses and detailed CI/CD logs for your pull requests.

Can I automate pull request verification to prevent merge conflicts?

Yes, you can automate pull request verification to prevent merge conflicts and ensure code quality. This Skill automates checking if all CI/CD tests and builds pass, confirming new code doesn't break the build or introduce regressions.

Why does my pull request CI check keep failing before merge?

Your pull request CI check may be failing due to test errors or build breaks. Use this Skill to view detailed workflow logs and identify the exact root cause of the CI failure before attempting to merge your code.