gh-check-ci-status

Check CI/CD status of a pull request including workflow runs and test results. Use when verifying if PR checks are passing or investigating CI failures.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill streamlines the DevOps workflow by providing real-time monitoring and management of GitHub CI/CD pipelines. It enables developers to verify Pull Request status, investigate workflow failures, and access detailed test logs directly within the chat interface, significantly reducing context switching and accelerating the path to production.

Use Cases

  • Verifying PR Readiness: Quickly confirm if all automated tests, linting, and security checks have passed before merging code to the main branch.
  • Investigating CI Failures: Retrieve and analyze logs from failed workflow runs to identify specific code errors or environment issues without leaving the terminal or IDE.
  • Real-time Workflow Monitoring: Track the progress of long-running CI jobs and receive updates on pending or skipped tasks to optimize development efficiency.
  • Pre-merge Validation: Ensure the latest commits are fully validated and the branch is up-to-date with base requirements to maintain repository health.
namegh-check-ci-status
description"Check CI/CD status of a pull request including workflow runs and test results. Use when verifying if PR checks are passing or investigating CI failures."
categorygithub

Check CI Status

Verify CI/CD status of a pull request and investigate failures.

When to Use

  • Verifying PR is ready to merge
  • Investigating CI failures
  • Monitoring long-running CI jobs
  • Checking before pushing changes

Quick Reference

# Check PR CI status
gh pr checks <pr>

# Watch CI in real-time
gh pr checks <pr> --watch

# Get detailed status
gh pr view <pr> --json statusCheckRollup

# View failed logs
gh run view <run-id> --log-failed

# Rerun failed checks
gh run rerun <run-id>

Workflow

  1. Check status: Run gh pr checks <pr> to see all checks
  2. Identify failures: Look for ✗ (failed) or ○ (pending)
  3. View logs: Use gh run view to see failure details
  4. Fix locally: Reproduce issue locally and test
  5. Push fix: Commit and push changes
  6. Verify: Watch CI with --watch flag

Common CI Failures

Pre-commit issues (formatting/linting):

just pre-commit-all  # Fix locally
git add . && git commit --amend --no-edit
git push --force-with-lease

Test failures:

mojo test tests/          # Run locally
pytest tests/             # Python tests
# Fix code and retest

Workflow validation:

gh workflow view <name>   # Check syntax
gh run rerun <run-id>     # Rerun failed

Status Indicators

  • ✓ - Passing
  • ✗ - Failed
  • ○ - Pending/In progress
  • - - Skipped

Error Handling

Problem Solution
No checks found PR may not trigger CI (check workflow)
Pending forever Check logs for stuck jobs
Auth error Verify gh auth status
API rate limit Wait or authenticate properly

Pre-Merge Verification

Before merging:

  • All required checks passing
  • No pending checks
  • Latest commit has checks
  • Branch up-to-date with base
gh pr checks <pr>          # All passing?
gh pr view <pr>            # Up-to-date?
gh pr diff <pr>            # Changes correct?

References

  • See .github/workflows/ for CI configuration
  • See CLAUDE.md for development workflow