skills.rest
openshift-eng
openshift-engOFFICIAL
Explore all skills by this author →
WebsiteGitHub

microshift-dev:golang-cve-analyzer

Validates MicroShift CVE tickets against Brew golang changelog nightly builds.

7|15|Updated Jan 23, 2026
Search Tags:#golang#jira#security validation#brew#cve analysis#release triage#microshift
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-dev-golang-cve-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microshift-dev:golang-cve-analyzer
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/microshift-dev/skills/golang-cve-analyzer
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-dev-golang-cve-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determining whether a MicroShift CVE Jira ticket is already fixed in the Go toolchain used by the latest MicroShift nightly Brew build can be slow and uncertain.

Core Features & Use Cases

  • CVE Ticket Validation: Confirms the Jira issue is a MicroShift ticket and extracts CVE IDs from its summary/description.
  • Version Targeting (X.Y): Infers the relevant OpenShift minor version from fixVersions, versions, or the ticket title.
  • Brew Golang CVE Cross-Check: Fetches CVE data from the Brew nightly golang changelog and reports which ticket CVEs are fixed vs missing, with an optional verbose breakdown.

Quick Start

Run: /microshift-dev:golang-cve-analyzer OCPBUGS-12345

Frequently Asked Questions about microshift-dev:golang-cve-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a MicroShift Jira CVE is fixed in the golang toolchain?▼

The analyzer validates MicroShift Jira CVE tickets against the Go toolchain used by the latest MicroShift nightly Brew build. It extracts CVE IDs from the ticket, fetches golang changelog data from Brew, and reports OK or MISSING results for each CVE.

How does CVE analysis infer the OpenShift minor version from a Jira ticket?▼

CVE analysis infers the OpenShift X.Y minor version by parsing fixVersions, versions, or the title metadata from the Jira ticket. This version targets the correct nightly Brew build to retrieve golang changelog data for validation.

Do I need Jira and Brew API access to run release triage for MicroShift?▼

Yes, you need Jira MCP access to fetch ticket details and Brew API access to retrieve golang changelog data. These dependencies are required to extract CVE IDs and verify their fix status against the nightly build toolchain.

What does it mean if the golang CVE cross-check reports a MISSING result?▼

A MISSING result means the CVE ID extracted from the MicroShift Jira ticket is not found in the golang changelog of the targeted nightly Brew build. This indicates the vulnerability remains unresolved in that specific Go toolchain version.

Can I get a verbose breakdown of CVE validation results for MicroShift nightly builds?▼

Yes, you can enable optional verbose reporting to get a detailed breakdown of the CVE validation results. This provides a comprehensive view of which ticket CVEs are fixed or missing across the Brew golang changelog.

Related Skills

Explore More Software Engineering Skills→
flurdyflurdy
6

jira-ticket

Fetch Jira ticket details and map issue types to branch prefixes.

Community
Intermediate
fullykubedfullykubed
2

CVE

Triage and resolve CVE vulnerabilities reported by vulnix in NixOS systems.

Community
Advanced
openshift-engopenshift-eng
7

microshift-release:pre-check

Check MicroShift release schedule, lifecycle, and payload availability for OCP releases.

Official
Advanced
riddopicriddopic

audit-context-building

Analyze functions line-by-line to document assumptions, invariants, and dependencies.

Community
Advanced