ga-regression-reports

Add a Component Readiness triage record link to a JIRA issue description

Grade component health based on regression triage metrics for OpenShift releases

Use when checking a repository's .coderabbit.yaml (or .coderabbit.yml) to determine whether inheritance: true is set

Fork, sync, and open a fix PR to add inheritance: true to a repo's .coderabbit.yaml

Fetch and analyze component health regressions for OpenShift releases

Analyze and compare disruption across one or more Prow CI job runs by examining interval data, audit logs, pod logs, and CPU metrics

Analyze a payload (rejected, accepted, or in-progress) with historical lookback to identify root causes of blocking job failures and produce an HTML report

Report on CodeRabbit adoption across OpenShift org PRs

Search for an existing fix PR on a repo before opening a new one

Search for repos with .coderabbit.yaml files in the openshift GitHub org

Fetch and filter human review comments from recent merged PRs in a GitHub repository

Fetch JIRA issue details including status, assignee, comments, and progress classification

Fetch a Prow job run summary from Sippy showing all failed tests grouped by SIG with error messages

Fetch pull requests that are new in a given OpenShift payload compared to the previous payload

Fetch recent release payloads from the OpenShift release controller

Fetch and return key data from a Prow job's prowjob.json artifact given a Prow job URL

Fetch detailed information about a Component Readiness regression from the Sippy API

Fetch existing triages and untriaged regressions related to a given regression

Fetch available OpenShift releases from the Sippy API

Fetch an OpenShift CI test report by name to get pass rates, test ID, and Jira component from Sippy

Fetch test runs from Sippy API including outputs for AI-based similarity analysis

Fetch OpenShift release dates and metadata from Sippy API

List all OCPBUGS components, optionally filtered by team

Query and return raw JIRA bug data for a specific project

List all teams from the team component mapping

Helper skill to retrieve OAuth tokens from the correct OpenShift cluster context when multiple clusters are configured

Schema for the autodl JSON data file produced by analyze-payload for database ingestion — you must use this skill whenever generating the autodl JSON file

Experimentally test medium-confidence payload candidates by opening draft revert PRs and triggering payload jobs

State management for agentic payload triage actions — you must use this skill whenever reading or writing the payload results YAML file

Analyze OpenShift installation failures in Prow CI jobs by examining installer logs, log bundles, and sosreports. Use when CI job fails "install should succeed" tests at bootstrap, cluster creation or other stages.

Analyze OpenShift bare metal installation failures in Prow CI jobs using dev-scripts artifacts. Use for jobs with "metal" in name, for debugging Metal3/Ironic provisioning, installation, or dev-scripts setup failures. You may also use the prow-job-analyze-install-failure skill with this one.

Analyze Kubernetes resource lifecycle in Prow CI job artifacts by parsing audit logs and pod logs from GCS, generating interactive HTML reports with timelines

Analyze failed Prow CI tests by inspecting test code, downloading artifacts, and optionally integrating must-gather cluster diagnostics for root cause analysis

Search, list, and fetch artifacts from Prow CI job runs stored in GCS using the gcloud CLI

Extract and decompress must-gather archives from Prow CI job artifacts, generating an interactive HTML file browser with filters

Git revert workflow and Revertomatic PR template for reverting merged PRs

Set the Release Blocker field on a JIRA issue

Create TRT JIRA bugs, open revert PRs, and trigger payload jobs for high-confidence revert candidates

Query and summarize JIRA bugs for a specific project with counts by component

Create or update a Component Readiness triage record linking regressions to a JIRA bug