From prega-release-notes
Generates Markdown release notes for a user-specified list of OLM package names from a catalog index image using opm render, default-channel head bundles, and ClusterServiceVersion data extracted with oc image extract. Use when the user asks for subset or partial release notes, per-operator notes, or passes package names with an index image (e.g. quay.io/prega/prega-operator-index:tag).
How this skill is triggered — by the user, by Claude, or both
Slash command
/prega-release-notes:subset-release-notesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill applies to the **prega-release-notes** repository layout: all commands below assume the working directory is the root of that repository (the folder containing `requirements.txt`, `bin/`, and `scripts/`).
This skill applies to the prega-release-notes repository layout: all commands below assume the working directory is the root of that repository (the folder containing requirements.txt, bin/, and scripts/).
pip install -r requirements.txtoc (always for bundle extract) and opm (unless --rendered-json is used).DOCKER_CONFIG (directory with config.json), REGISTRY_AUTH_FILE, or --authfile.oc or opm is missingFast path (this repo): run python3 scripts/bootstrap_clients.py (or ./scripts/bootstrap_clients.py if executable) after setting OCP_VERSION to match the index (e.g. 4.20 for stable-4.20, or 4.22.0-ec.0 for dev-preview). Binaries land in <repo>/bin/. Then:
export PATH="/path/to/prega-release-notes/bin:$PATH"
CLI integrated path: pass --auto-install-clients (or set PREG_RELEASE_NOTES_AUTO_INSTALL_CLIENTS=1) so release_notes_subset.py runs bootstrap_clients.py automatically before resolving tools. Use --ocp-version (or env OCP_VERSION) to pick the mirror channel.
Broader / manual installs (Helm, ROSA, checksum-first flows, ambiguous versions): follow .cursor/skills/openshift-client-download/SKILL.md, adapted from ai-helpers@b0e2950.
The CLI prefers <repo>/bin/oc and <repo>/bin/opm over unrelated binaries on PATH when both exist.
cd /path/to/prega-release-notes
export DOCKER_CONFIG=/path/to/dir_containing_config_json
pip install -r requirements.txt
chmod +x bin/prega-release-notes scripts/bootstrap_clients.py # once (optional; can use python3 path)
./bin/prega-release-notes --auto-install-clients --ocp-version 4.20 \
--index quay.io/prega/prega-operator-index:v4.22.0-ec.0 \
--packages ocs-operator \
--packages metallb-operator \
-o subset-release-notes.md
Equivalent:
python3 scripts/release_notes_subset.py --auto-install-clients …
Comma-separated packages in one flag are allowed, for example --packages ocs-operator,odf-operator.
opm render <index> --output=json (unless --rendered-json points at a saved NDJSON file for offline use).olm.package → defaultChannel, then the latest bundle entry on that channel (version order matches sort -V).olm.bundle image for that head bundle and runs oc image extract … --path /manifests:..*clusterserviceversion.yaml under manifests/ and emits Markdown (display name, version, container image, stripped description, related images).Use --opm-timeout 0 for an unlimited opm render wait (default is 7200 seconds).
The file starts with a title and short preamble, then one ## section per successful package, then a Skipped or failed packages section if any package could not be resolved or extracted.
After the script succeeds, the agent may tighten wording, group related operators, or align tone with team release-note style—without removing factual fields (versions, image references, package names).
cd /path/to/prega-release-notes
./bin/prega-release-notes \
--rendered-json tests/fixtures/release_notes_subset/index.jsonl \
-p operator-a \
-o out.md
Still requires oc and registry access for a real bundle pull unless extraction is mocked; unit tests: python3 -m unittest tests.test_release_notes_subset -v.
Copy .cursor/skills/subset-release-notes (and optionally openshift-client-download) into another project’s .cursor/skills/, or open prega-release-notes as the Cursor workspace root so skills load automatically.
For Claude Code, copy .claude/commands/subset-release-notes.md and .claude/commands/download-clients.md into the target project’s .claude/commands/.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub midu16/prega-release-notes --plugin prega-release-notes