skills.rest
openshift-eng
openshift-engOFFICIAL
Explore all skills by this author →
WebsiteGitHub

microshift-ci:doctor-refresh

Regenerate the MicroShift CI Doctor HTML report from existing bug mapping JSON files.

7|15|Updated Jan 23, 2026
Search Tags:#refresh#doctor#html report#ci debugging#microshift-ci#bug mapping
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-ci-doctor-refresh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microshift-ci:doctor-refresh
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/microshift-ci/skills/doctor-refresh
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-ci-doctor-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

You need an up-to-date CI Doctor HTML report after bug creation, without re-running expensive CI analysis or JIRA queries.

Core Features & Use Cases

  • Refresh an existing report: Rebuilds the CI Doctor HTML using already-generated artifacts and bug mapping outputs.
  • Validates required mapping inputs: Checks that the expected analyze-ci-bugs-*.json files exist for the requested releases (and known rebase sources) before generating.
  • Fast “regenerate only” workflow: Does not re-analyze jobs, re-aggregate summaries, or re-query JIRA, so it’s safe for incremental updates after /microshift-ci:create-bugs --create.

Quick Start

Run the command to refresh the report for the releases you want, for example: /microshift-ci:doctor-refresh 4.19,4.20,4.21,4.22

Frequently Asked Questions about microshift-ci:doctor-refresh

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

FAQPage Schema
How do I regenerate a CI Doctor HTML report without rerunning expensive CI analysis?▼

Use a doctor refresh workflow to rebuild the CI Doctor HTML report from existing bug mapping data, skipping CI analysis and JIRA queries. It uses already-generated artifacts to produce an updated report reflecting newly created bugs.

What inputs are required to refresh the MicroShift CI Doctor HTML report?▼

Refreshing the CI Doctor HTML requires an existing dated workdir and analyze-ci-bugs JSON mapping files for the specified releases. The process validates that these expected mapping inputs exist before generating the updated report.

When should I use a doctor refresh instead of rerunning full CI bug analysis?▼

Use a doctor refresh for incremental updates after creating bugs, when you need the HTML updated to reflect newly created bugs. It does not re-analyze jobs, re-aggregate summaries, or re-query JIRA, making it safe for fast report regeneration.

How do I specify multiple releases when refreshing the CI Doctor report?▼

Pass a comma-separated list of releases, such as 4.19,4.20,4.21,4.22, to the refresh command. The process checks for analyze-ci-bugs JSON mapping files for each requested release and known rebase sources before generating.

Does the doctor refresh workflow re-query JIRA or re-aggregate CI summaries?▼

No, the doctor refresh workflow does not re-query JIRA, re-analyze jobs, or re-aggregate summaries. It strictly regenerates the CI Doctor HTML from existing bug mapping data to provide a fast incremental update.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng
7

microshift-ci:create-bugs

Create USHIFT JIRA bug issues from MicroShift CI failure reports with dry-run default.

Official
Advanced
openshift-engopenshift-eng
7

microshift-ci:continue-session

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

Official
Intermediate
refactory-langrefactory-lang

speckit-workflows.bugfix

Create a Git branch and markdown bug report for a bug fix workflow.

Official
Intermediate
cosmixcosmix
53

ci-cd

Design and automate CI/CD pipelines for GitHub Actions, GitLab CI, and Jenkins.

Community
Advanced