// Regenerate the CI Doctor HTML report from existing data
Create JIRA bugs from analyze-ci failure reports with cross-release deduplication (dry-run by default)
Check OCP release schedule, verify availability, evaluate z-stream need, or check nightly build gaps
Run the full Prow CI release testing workflow — create PR, trigger jobs, check status, merge PR, download and upload artifacts
Analyze CI for multiple MicroShift releases and produce an HTML summary
Analyze CI for LVMS periodic jobs and produce an HTML summary
Download Prow job artifacts, identify root cause of failure, and produce a structured error report
| name | microshift-ci:doctor-refresh |
| argument-hint | <release1,release2,...> |
| description | Regenerate the CI Doctor HTML report from existing data |
| user-invocable | true |
| allowed-tools | Bash, Read, Glob |
/microshift-ci:doctor-refresh <release1,release2,...>
Regenerates the CI Doctor HTML report from existing data. Use this after /microshift-ci:create-bugs --create to update the report with newly created bugs.
This is a lightweight operation: it does not re-analyze jobs, re-aggregate summaries, or re-query JIRA. It reads the existing bug mapping files (which include newly created bugs via the create-bugs Step 4b update) and regenerates the HTML.
<ARGUMENTS> (required): Comma-separated list of release versions (e.g., 4.19,4.20,4.21,4.22)Compute once at the start by running date +%y%m%d and substituting into the path below. In all commands, replace <WORKDIR> with the computed path.
/tmp/microshift-ci-claude-workdir.<YYMMDD>
Compute today's <WORKDIR> by running date +%y%m%d and substituting into /tmp/microshift-ci-claude-workdir.<YYMMDD>.
Verify the directory exists. If it does not:
Error: no workdir found at <WORKDIR>
Run the full doctor workflow first: /microshift-ci:doctor <releases>
Parse <ARGUMENTS> into a list of release versions.
Check for rebase PR sources in the workdir by looking for analyze-ci-bug-candidates-rebase-release-*.json files. Extract the source identifiers (e.g., rebase-release-4.22).
Verify that <WORKDIR>/analyze-ci-bugs-<source>.json exists for each release version and each rebase PR source.
If any mapping files are missing, report which ones are missing and show an error:
Error: bug mapping files missing for: <sources>
Run the full create-bugs workflow first: /microshift-ci:create-bugs <sources> --create --auto
Continue to Step 3 anyway — the HTML report will be generated with whatever data is available.
Do NOT delete bug mapping files. Do NOT launch create-bugs agents. The mapping files are produced by the preceding /microshift-ci:create-bugs session and include newly created bugs (via Step 4b of the create-bugs skill).
Run the refresh script:
bash plugins/microshift-ci/scripts/doctor.sh refresh --component microshift --workdir <WORKDIR> <ARGUMENTS>
Display the path to the regenerated HTML report.
/microshift-ci:doctor-refresh 4.19,4.20,4.21,4.22
/microshift-ci:doctor-refresh 4.22
/microshift-ci:doctor run/microshift-ci:create-bugs run/microshift-ci:create-bugs run