Menú
Download CI Doctor artifacts from a completed prow job and set up a local workdir for continued analysis
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Surface your daily task list — QA-ready tickets, sprint backlog, carry-over items, open PRs, RHEL verification queue, and quarterly reminders. Use at the start of your day to see what needs attention.
Show detailed info about a specific TODO task — its tracked links, notes, and live Jira/PR status. Use when the user asks about a task, wants context to resume work on it, or asks what's needed to finish a ticket. Not for listing all tasks (read the TODO file directly or use edge-ic:sprint-status for sprint-wide views)
End-of-week automation - review active work and prepare next week's TODO
Run the full Prow CI release testing workflow — create PR, trigger jobs, check status, merge PR, download and upload artifacts
Generate interactive PCP performance dashboard from a Prow job URL
Download Prow job artifacts, identify root cause of failure, and produce a structured error report
| name | microshift-ci:continue-session |
| argument-hint | <prow-job-url> |
| description | Download CI Doctor artifacts from a completed prow job and set up a local workdir for continued analysis |
| user-invocable | true |
| allowed-tools | Bash, Read, Glob, Grep |
/microshift-ci:continue-session https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-eng-edge-tooling-main-microshift-ci-doctor/2053152146479648768
Downloads CI Doctor analysis artifacts (per-job reports, summaries, bug mappings, HTML report) from a completed prow job into a local workdir, preserving the source directory structure. The workdir date is derived from the prow job's start timestamp, matching the layout the doctor skill creates. This lets you pick up where the CI agent left off — inspect reports, re-run aggregation, create bugs, or do further investigation.
<ARGUMENTS> (required): A Prow job URL or GCS web URL pointing to a CI Doctor job runRun the download script:
bash plugins/microshift-ci/scripts/continue-session.sh <ARGUMENTS>
The script:
started.json to derive the job date → workdir path<WORKDIR>/jobs/ — job analysis files (release-*, prs-*)<WORKDIR>/bugs/ — bug correlation files (bugs-*, bug-candidates-*)<WORKDIR>/ — final reports (HTML report, claude logs)Read the JSON summary. It contains:
workdir — local path where files were downloadedreleases — array of releases with job report counts, summary/bugs availabilityprs — PR job report info (or null)html_report — path to the HTML report (or null)files_downloaded — total file countPresent the summary to the user:
Suggest next actions based on what's available:
View the HTML report: open <workdir>/report-microshift-ci-doctor.html
Re-generate the HTML report (e.g., after modifying job reports):
bash plugins/microshift-ci/scripts/doctor.sh finalize --component microshift --workdir <WORKDIR> <RELEASES>
where <RELEASES> is a comma-separated list of the releases found in the summary.
Create Jira bugs from the analysis:
/microshift-ci:create-bugs <VERSION> --create
Read individual job reports for deeper investigation:
<WORKDIR>/jobs/release-<VERSION>-job-<N>-<BUILD_ID>.txt
Re-analyze a specific prow job (downloads fresh artifacts):
/microshift-ci:prow-job <PROW_URL>
gsutil CLI must be installed (uses anonymous access on public GCS buckets)jq for JSON processing/microshift-ci:prow-job or download-jobs.sh to fetch those for specific jobs./tmp/microshift-ci-claude-workdir.<YYMMDD>), with job analysis files under jobs/ and bug correlation files under bugs/. All doctor scripts (finalize, aggregate.py, create-report.py) work directly on the downloaded data.