microshift-ci:test-job

Fetch Prow CI job metadata and aggregate MicroShift test scenario results into JSON and Markdown reports.

7|15|Updated Jan 23, 2026

Search Tags:#prow-ci #ci troubleshooting #log triage #microshift #test scenario analysis #version extraction #gcs artifacts

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a MicroShift Prow CI job fails or needs review, it’s hard to quickly understand what was tested, which scenarios ran, and where to find the most relevant logs and artifacts.

Core Features & Use Cases

Job execution intelligence: Fetches Prow/GCS job metadata (status, timing, architecture, image type, job name/ID) and presents it as a readable report.
MicroShift version extraction: Derives the exact MicroShift build/version for the job by extracting it from build logs (via the provided helper).
Scenario-by-scenario analysis: Enumerates test scenarios and aggregates per-scenario results (including failure details and artifact links) for fast triage.
Useful for: Engineers investigating CI regressions, validating coverage before releases, and quickly collecting evidence for bug reports or release candidate decisions.

Quick Start

Provide the Prow job URL to microshift-ci:test-job and ask it to produce a full Markdown report with the status, MicroShift version, scenario outcomes, and links to logs and artifacts.

Frequently Asked Questions about microshift-ci:test-job

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

FAQPage Schema

How do I analyze a MicroShift Prow CI job from a URL?▼

To analyze a MicroShift Prow CI job, provide the Prow job URL to fetch started and finished metadata, extract the MicroShift version from build logs, and aggregate per-scenario test outcomes into a structured report.

How can I find the exact MicroShift version used in a failed Prow CI test?▼

You can find the exact MicroShift version by parsing the job configuration and extracting the build version from the CI logs using a helper script, which then aggregates this data into a comprehensive Markdown report.

What is the best way to triage scenario failures across different architectures in Prow CI?▼

The best way to triage scenario failures is to enumerate test scenarios and aggregate per-scenario results, including failure details and artifact links, across different architectures and image types into a single JSON and Markdown report.

Can I use a job ID instead of a URL to troubleshoot MicroShift CI test executions?▼

Yes, you can use a specific job ID as input to fetch Prow and GCS job metadata, parse job configuration, and generate a readable report with status, timing, architecture, and image type details.

How do I collect GCS artifact and log links for a MicroShift Prow job review?▼

To collect GCS artifact and log links, the analysis process fetches job execution intelligence and iterates through test scenarios, returning both JSON and Markdown formats with direct links to relevant artifacts.

Does this CI log triage process work for validating MicroShift release candidates?▼

Yes, this CI log triage process works for validating coverage before releases by providing engineers with job execution intelligence and scenario-by-scenario analysis to quickly collect evidence for release candidate decisions.