microshift-ci:prow-job

Analyzes Prow build logs to identify failing CI steps and classify root causes for MicroShift workflows.

7|15|Updated Jan 23, 2026

Search Tags:#root cause analysis #failure classification #ci triage #ci log analysis #microshift #prow job artifacts #sos report

Ready to run

npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-ci-prow-job

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: microshift-ci:prow-job
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/microshift-ci/skills/prow-job
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-ci-prow-job

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces noisy Prow CI log triage by downloading job artifacts (or using local artifacts), locating the failing step, and producing a structured error report for MicroShift CI failures.

Core Features & Use Cases

Artifact-based failure diagnosis: Downloads and scans top-level build logs plus step logs to find fatal errors and their locations.
Root-cause oriented classification: Determines whether failures are legitimate test failures or CI/infra failures, and identifies the pipeline stack layer.
SOS report deep dive: Extracts relevant evidence from MicroShift-related SOS artifacts to characterize microshift/journal/pod issues.
Use Case: When a MicroShift e2e job fails with thousands of log lines, this Skill helps pinpoint the failing step and provides a remediation-ready report with a structured summary.

Quick Start

Run /microshift-ci:prow-job with the full Prow job URL you want analyzed.

Frequently Asked Questions about microshift-ci:prow-job

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

FAQPage Schema

How do I analyze Prow CI logs to find the root cause of a MicroShift test failure?▼

Analyzing Prow CI logs for MicroShift failures involves scanning build-log and step-log artifacts to pinpoint the failing step and summarize the root cause. This classifies whether the failure is a legitimate test issue or a CI infrastructure problem.

What is the best way to triage noisy MicroShift e2e job failures?▼

The best way to triage noisy MicroShift e2e failures is by processing Prow job artifacts to locate the failing step. This generates a structured report that distinguishes legitimate test failures from CI infrastructure issues.

Can I use a local artifacts directory instead of downloading Prow job artifacts for CI log analysis?▼

Yes, you can use a local artifacts directory for CI log analysis if it contains the required build-log.txt and finished.json files. This allows you to perform failure classification and root cause analysis without downloading artifacts directly from Prow or GCS.

How does SOS report extraction work for MicroShift CI failure classification?▼

SOS report extraction for MicroShift CI failure classification works by scanning MicroShift-related SOS artifacts to characterize journal and pod issues. This provides relevant evidence to determine whether a failure originates from the test logic or the infrastructure stack layer.

Do I need specific files to classify Prow CI failures as test or infrastructure issues?▼

Yes, you need the build-log.txt and finished.json files to classify Prow CI failures accurately. These files provide the necessary context to determine if an error is a legitimate test failure or a CI infrastructure issue within the MicroShift pipeline.