skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
redhat-developer/rhdh-skills48 installs

rhdh-overlay-cve-export

Builds the "RHDH CVE Management - <version>-plugins.csv" export by walking `rhdh-plugin-export-overlays` git history on a release branch since a revision, scoped to generally-available plugin workspaces, then enriching each CVE from Jira RHIDP, RHDHBUGS, and RHDHPLAN. Use for "generate the plugin overlay CVE CSV for 1.10.3", "what CVEs were fixed in plugins since 1.10.2", or "rebuild the plugin CVE list with the ProdSec CVSS scores".

How do I install this agent skill?

npx skills add https://github.com/redhat-developer/rhdh-skills --skill rhdh-overlay-cve-export
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill automates the creation of CVE reports for Red Hat Developer Hub plugins by analyzing the git history and pull request data of the rhdh-plugin-export-overlays repository. It uses standard system tools like Git and the GitHub CLI and follows secure practices, such as sanitizing CSV output and restricting operations to vendor-owned repositories.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Plugin overlay CVE export

Turn overlays git history into the CSV that RHDH CVE Management expects: one row per CVE and affected plugin package, scoped to generally-available workspaces.

This is a package-inventory job, not release reporting. It answers "which plugin containers carry which CVE fix", from git — not "how is the release doing", which is /rhdh-release-status.

Route

Load workflows/overlay-cve-export.md. It covers the extract run, Jira enrichment, and the flag set.

Two references belong to this workflow alone and are read on demand:

  • references/overlay-cve-csv-format.md — the exact header, the row rule, the Container column, and the default output path.
  • references/overlay-cve-sources.md — which workspaces and commits count, how CVEs and Jira keys are extracted, and how --since resolves.

Do not reimplement the parsing

scripts/compute-plugin-package-overlay-cve-list.mjs owns commit selection, CVE extraction, pairing, dedupe, and CSV shape. Run it. Reading the overlays repo by hand and assembling rows in chat produces a different answer than the export the CVE process is checked against.

The script never calls Jira. Enrichment is a separate pass: invoke /rhdh-jira-api for the issue fields, write them to a JSON file, and feed that back through --apply-enrich.

Writing rules

The extract itself only clones and reads. Writing the enrichment JSON and the final CSV creates files on the user's disk — say where they will land and get agreement before the run that writes them. Never commit the CSV into a repository, and never post it anywhere.

Completion

Complete when the CSV path is named, the row count is stated, and the --since revision the script actually resolved is reported rather than the version string that was asked for. Every CVE without a Jira issue is listed with the overlays commit URL that stands in for it. CVSS appears only where a ProdSec CVSS field supplied it — a blank CVSS column is the correct output, never a filled-in guess. Rows dropped by the --jql filter are counted, so the user can tell an empty result from a filtered one. No credential or OAuth secret appears in any output.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/redhat-developer/rhdh-skills/rhdh-overlay-cve-export">View rhdh-overlay-cve-export on skillZs</a>