with one click
ci-health
ci-health contains 16 collected skills from kubevirt, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Analyze the root cause inside a failed prowjob. Use when user mentions to analyze a prowjob failure or adds a prowjob url
Analyze root causes for all the recent ci-failures. Use when user mentions to analyze recent ci failures
Analyze all failed builds for a GitHub pull request. Use when user provides a GitHub PR URL and wants to understand why builds are failing.
Analyze the root cause inside a failed prowjob when a user mentions a failure or adds a prowjob URL.
Analyze root causes for all the recent CI failures (failing prowjobs that have not reached the testing stage).
Analyze all failed builds for a GitHub pull request and identify root causes.
Unified flake analysis combining PR-based flakefinder data with periodic lane failure rates. Use when the user wants an overview of test flakiness across the project.
Analyze failure rates and flakiness patterns for all tests in a testgrid lane. Uses flip-rate analysis, burst detection, and cross-test correlation in addition to success rates. Use when the user provides a testgrid URL and wants to see which tests are failing in that lane.
Analyze test failures from a Prow build against historical flakefinder data. Classifies failures as flaky, PR-related, or infrastructure-related using success rates, failure dispersion across lanes, and cross-test correlation.
Determine whether a PR's code changes are related to tests that failed in a Prow build.
Provide a unified flake analysis combining GCS-based flakefinder reports with testgrid success rates.
Analyze failure rates, flip-rates, and flakiness patterns for all tests in a testgrid lane.
Analyze test failures from a Prow build against historical 7-to-28 day flakefinder reports.
Identify and retrigger missing or failed required Prow status checks for a GitHub pull request.
Trigger missing or failed required status checks for a GitHub pull request. Use when user provides a GitHub PR URL and wants to retrigger failed or missing CI jobs.
Determine whether a PR's code changes are related to tests that failed in a Prow build. Use when user wants to know if test failures are caused by their PR changes.