plugins/ci/skills/fetch-payloads/SKILL.md
Fetch recent release payloads from the OpenShift release controller
npx skillsauth add openshift-eng/ai-helpers fetch-payloadsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill fetches recent release payloads from the OpenShift release controller, showing their tag name, acceptance phase, timestamp, blocking job results, and a link to the release details page.
Use this skill when you need to:
If the user did not specify an architecture or stream, default to amd64 and nightly. If no version is specified, the script automatically fetches the latest from the Sippy API.
FETCH_PAYLOADS="${CLAUDE_PLUGIN_ROOT}/skills/fetch-payloads/fetch_payloads.py"
if [ ! -f "$FETCH_PAYLOADS" ]; then
FETCH_PAYLOADS=$(find ~/.claude/plugins -type f -path "*/ci/skills/fetch-payloads/fetch_payloads.py" 2>/dev/null | sort | head -1)
fi
if [ -z "$FETCH_PAYLOADS" ] || [ ! -f "$FETCH_PAYLOADS" ]; then echo "ERROR: fetch_payloads.py not found" >&2; exit 2; fi
python3 "$FETCH_PAYLOADS" [architecture] [version] [stream]
Examples:
# Latest amd64 nightly payloads (all defaults, last 5)
python3 "$FETCH_PAYLOADS"
# arm64 4.18 nightly
python3 "$FETCH_PAYLOADS" arm64 4.18 nightly
# Only accepted payloads
python3 "$FETCH_PAYLOADS" amd64 4.18 nightly --phase Accepted
# Show more results
python3 "$FETCH_PAYLOADS" amd64 4.18 nightly --limit 20
The script outputs one block per payload to stdout with job details. Present to the user as-is or summarize.
The script outputs a JSON object to stdout:
{
"hours_since_last_accepted": 23.5,
"last_accepted_tag": "4.22.0-0.nightly-2026-02-24-030944",
"payloads": [ ... ]
}
hours_since_last_accepted: Hours since the most recent Accepted payload in the stream (from the full unfiltered history), or null if none found.last_accepted_tag: Tag name of the most recent Accepted payload, or null if none found.payloads: Array of payload objects, each containing tag, phase, release controller URL, and job results (blocking and async jobs with Prow URLs and retry details).tools
Analyze a JIRA issue and create a pull request to solve it. Use when the user wants to implement a fix or feature described in a Jira issue, push a branch, and open a draft PR.
development
Use when a deeper level of code review is requested. Multi-agent panel code review with specialist reviewers and forced runtime reproducers for all BLOCKING bug findings. Optionally posts to GitHub/GitLab as a PENDING review.
development
Review agentic documentation — verify claims locally against source code first, then use chai-bot for cross-repo and cross-functional verification
development
Use this skill when debugging a failed Prow CI job.