investigate-ci-failure

Diagnose CI/Prow failures for GitHub PRs using gh CLI data.

71|88|Updated Nov 8, 2023
One-click install
npx skills add https://github.com/openshift/lightspeed-service --skill investigate-ci-failure-openshift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate-ci-failure
Source: https://github.com/openshift/lightspeed-service/tree/main/.cursor/skills/investigate-ci-failure
Command: npx skills add https://github.com/openshift/lightspeed-service --skill investigate-ci-failure-openshift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI failures on PRs can be time-consuming to diagnose; this Skill automates extraction of PR metadata, check statuses, and failure context to generate a concise failure analysis.

Core Features & Use Cases

  • Extract PR metadata (org, repo, PR number) and current statuses
  • Retrieve failing checks, detailed statuses, and relevant artifact logs
  • Cross-reference PR changes to identify potential PR-related issues and provide remediation steps
  • Produce a structured diagnostic report with next steps and links to logs/dashboards
  • Use cases include debugging flaky tests, triaging failing CI jobs, and preparing for PR review

Quick Start

Paste a PR URL to trigger a CI failure analysis and get a structured diagnostic.

Frequently Asked Questions about investigate-ci-failure

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

FAQPage Schema
How do I diagnose PR CI failures from a GitHub URL?

Diagnose PR CI failures by pasting a GitHub PR URL to automatically extract metadata, fetch Prow check statuses, and retrieve artifact logs for a structured diagnostic report with actionable next steps.

What is the best way to triage failing Prow checks across OpenShift projects?

Triage failing Prow checks by leveraging gh CLI calls to fetch PR data and statuses, cross-referencing PR changes to identify issues, and generating concise failure analyses with remediation steps.

Can I debug flaky tests using GitHub PR statuses and artifacts?

Debug flaky tests by retrieving detailed failing check statuses and relevant artifact logs, cross-referencing PR changes to pinpoint instability and provide remediation steps.

Does this CI failure analysis tool work with standard GitHub pull requests?

It works with standard GitHub pull requests by extracting PR metadata such as org, repo, and PR number, fetching current statuses and failing checks to produce structured failure analyses.

How do I get links to logs and dashboards for failing CI jobs?

Get links to logs and dashboards by triggering a CI failure analysis with a PR URL, which fetches artifact logs and returns a structured diagnostic report with direct links to logs and dashboards.