plugins/ci/skills/fetch-releases/SKILL.md
Fetch available OpenShift releases from the Sippy API
npx skillsauth add openshift-eng/ai-helpers fetch-releasesInstall 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 the list of available OpenShift releases from the Sippy API. It can return all OCP releases or just the latest version.
Use this skill when you need to:
Python 3: Python 3.6 or later
python3 --versionNetwork Access: Must be able to reach the public Sippy API
curl -s https://sippy.dptools.openshift.org/api/releases | head -c 100To get just the latest OCP release version:
release=$(python3 plugins/ci/skills/fetch-releases/fetch_releases.py --latest)
echo "$release"
# Output: 4.22
To list all available OCP releases:
# JSON format (includes GA dates)
python3 plugins/ci/skills/fetch-releases/fetch_releases.py --format json
# Simple list, one per line
python3 plugins/ci/skills/fetch-releases/fetch_releases.py --format list
The primary use case is providing a default release to other skills:
# Determine release
release="${user_specified_release:-$(python3 plugins/ci/skills/fetch-releases/fetch_releases.py --latest)}"
# Use with fetch-test-report
python3 plugins/ci/skills/fetch-test-report/fetch_test_report.py "<test_name>" --release "$release"
Prints a single release version string:
4.22
[
{"release": "4.22"},
{"release": "4.21", "ga": "2025-06-17T00:00:00Z"},
{"release": "4.20", "ga": "2025-10-21T00:00:00Z"},
{"release": "4.19", "ga": "2025-06-17T00:00:00Z"}
]
Releases without a ga field are still in development.
4.22
4.21
4.20
4.19
4.18
Exit Codes:
0: Success1: Errorhttps://sippy.dptools.openshift.org/api/releases (no port-forward needed)X.Y formatteams plugin's get-release-dates skillfetch-test-report (uses release to query test data)get-release-dates (fetches detailed release dates and metadata)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.