skills.rest
kagenti
kagentiOFFICIAL
Explore all skills by this author →
GitHub

ci:status

Retrieve CI status for a Pull Request and create follow-up tasks for failures.

292|103|Updated Mar 27, 2025
Search Tags:#automation#testing#debugging#pull request#github actions#ci
One-click install
npx skills add https://github.com/kagenti/kagenti --skill ci-status-kagenti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci:status
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/ci%3Astatus
Command: npx skills add https://github.com/kagenti/kagenti --skill ci-status-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a clear and actionable overview of your Pull Request's Continuous Integration (CI) status, highlighting any failures and their root causes.

Core Features & Use Cases

  • PR CI Status Check: Retrieves the current status of all CI checks for a given Pull Request.
  • Failure Identification: Pinpoints specific CI checks that have failed.
  • Detailed Failure Analysis: Downloads logs and test results for failed checks to aid in debugging.
  • Task Creation: Automatically generates tasks for identified failures, streamlining the debugging process.
  • Use Case: After pushing a code change to a PR, you can ask the AI "What's the CI status for PR #123?" and it will report the status, detailing any failures and creating tasks for you to investigate.

Quick Start

Check the CI status for the current pull request.

Frequently Asked Questions about ci:status

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

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

To check the CI status of a GitHub pull request, query the PR checks via GitHub CLI to retrieve the current status of all CI actions, pinpoint specific failures, and summarize the results for review.

What is the best way to download GitHub Actions logs for failed CI checks?▼

Downloading GitHub Actions logs for failed CI checks involves querying the PR run details via GitHub APIs to fetch relevant logs and test artifacts, aiding in debugging by identifying specific failure points.

Can I automatically create debugging tasks for failed GitHub Actions checks?▼

You can automatically create debugging tasks for failed GitHub Actions checks by identifying the failures during the CI status check and generating follow-up tasks to streamline root cause analysis.

Do I need GitHub CLI to monitor pull request CI failures?▼

You need GitHub CLI installed and configured to monitor pull request CI failures, as it requires access to GitHub CLI and associated APIs to query PR checks and retrieve detailed run information.

How does identifying failed CI checks help with debugging a pull request?▼

Identifying failed CI checks helps with debugging a pull request by pinpointing specific failures, downloading relevant logs and test artifacts, and creating tasks to investigate the root cause of the broken checks.

Why are my GitHub Actions checks failing on a pull request?▼

GitHub Actions checks may be failing on a pull request due to specific test or build errors; retrieving the CI status and downloading the run logs allows you to pinpoint the exact failures for debugging.

Related Skills

Explore More Software Engineering Skills→
granietgraniet
247

github-auth

Automates GitHub authentication setup for git, SSH, gh CLI, and API access.

Community
Intermediate
benzwickbenzwick

analyze-test-results

Diagnose failing tests and CI artifacts to pinpoint root causes.

Community
Advanced
pingqLINpingqLIN

gh-fix-ci

Diagnose and fix failing GitHub Actions checks on pull requests.

Community
Advanced
joegoldinjoegoldin
2

gh-checks

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

Community
Intermediate