microshift-ci:continue-session

Download CI Doctor artifacts from a completed Prow job into a local workdir.

7|15|Updated Jan 23, 2026

Search Tags:#debugging #analysis #artifacts #ci #prow #microshift #jira bugs

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gsutil, jq, bash, and includes scripts (resource) components.

What problem does it solve?

It solves the problem of having to manually re-collect and re-prepare CI Doctor analysis artifacts after a CI run so you can continue investigating results locally.

Core Features & Use Cases

Download CI Doctor artifacts from a completed prow job: Pulls per-job reports, summaries, bug mappings, and the HTML report into a correctly structured local workdir.
Continue the analysis workflow: Enables re-running aggregation/finalization and subsequent bug-creation steps using the same workdir layout as the doctor workflow.
Use Case: When a nightly or PR-related MicroShift CI Doctor job completes, you can resume review of the generated findings and open the HTML report without re-running the entire pipeline.

Quick Start

Run /microshift-ci:continue-session with the completed prow job URL to download the artifacts and get a ready-to-use local workdir and summary.

Frequently Asked Questions about microshift-ci:continue-session

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

FAQPage Schema

How do I resume MicroShift CI debugging from a completed prow job?▼

You can resume MicroShift CI debugging by providing a completed prow job URL to automatically download CI Doctor artifacts and set up a local work directory. This prepares per-job reports, summaries, and bug mappings for continued investigation without re-running the entire pipeline.

How do I download CI Doctor artifacts from a GCS path?▼

Downloading CI Doctor artifacts requires converting the prow job URL to a GCS path, then using gsutil to fetch started.json and derive the workdir date. The process uses jq to produce a JSON summary of downloaded releases and report availability.

Do I need gsutil and jq to continue Prow CI troubleshooting locally?▼

Yes, you need gsutil and jq installed locally to continue Prow CI troubleshooting. gsutil handles downloading artifacts from the GCS path, while jq parses JSON data to generate a summary of downloaded releases and report availability.

Can I re-run aggregation and finalization steps for MicroShift nightly CI results?▼

Yes, you can re-run aggregation and finalization steps for MicroShift nightly CI results. The downloaded artifacts create a correctly structured local workdir that enables re-running subsequent bug-creation steps using the same layout as the doctor workflow.

What is the best way to inspect Jira bugs mapped from MicroShift CI failures?▼

The best way to inspect Jira bugs mapped from MicroShift CI failures is to resume the CI Doctor session locally. This pulls per-job reports, summaries, and bug mappings into a local workdir for immediate review without re-running the entire pipeline.