ci-checker

Check GitHub CI status for pull requests and guide failure fixes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill ci-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-checker
Source: https://github.com/christian-byrne/ticket-to-pr-pipeline/tree/main/skills/ci-checker
Command: npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill ci-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers quickly identify the root cause of failing Continuous Integration (CI) checks on their pull requests and provides guidance on how to resolve them.

Core Features & Use Cases

  • CI Status Check: Retrieves the status of all CI checks associated with a pull request.
  • Failure Diagnosis: Provides detailed error messages and logs for failing checks.
  • Guided Remediation: Offers actionable steps and commands to fix identified issues locally.
  • Use Case: After pushing a change, a developer sees their PR checks failing. They invoke this Skill, which reports the specific failing tests, shows the relevant error output, and suggests running pnpm lint:fix locally to resolve the issue.

Quick Start

Use the ci-checker skill to diagnose the failing CI checks on pull request number 123.

Frequently Asked Questions about ci-checker

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

FAQPage Schema
How do I diagnose failing GitHub Actions checks on a pull request?

To diagnose failing GitHub Actions CI failures on a pull request, this skill retrieves check statuses via the gh CLI, parses logs for specific error messages, and suggests actionable remediation commands.

What is the best way to fix CI failures locally after pushing a change?

The best way to fix CI failures locally is to use guided remediation steps provided by the skill, which checks out the PR branch, analyzes the failing test logs, and offers specific commands to resolve the issues.

Does this CI checker require local checkout of the PR branch before executing checks?

Yes, the CI checker requires a local checkout of the PR branch before executing checks. It ensures this local checkout occurs prior to retrieving check statuses and parsing logs via the GitHub API.

Can I transition ticket states automatically upon successful CI completion?

Yes, you can transition ticket states automatically upon successful CI completion. The skill checks GitHub CI status for pull requests and can transition ticket states once all checks pass successfully.

Why are my pull request checks failing and how do I get the error output?

Your pull request checks may be failing due to linting or test errors. The skill retrieves the specific failing tests and shows the relevant error output by interacting with the GitHub API via the gh CLI.

What are the limitations of using gh CLI for diagnosing continuous integration failures?

Limitations of using gh CLI for diagnosing continuous integration failures include dependency on the GitHub API for check statuses and the requirement to have a local checkout of the PR branch before executing checks and parsing logs.