openshift-eng-ai-helpers

Plugin openshift-eng-ai-helpers from marketplace cascade-code-devops-misc-1 in joshuarweaver/cascade-code-devops-misc-1. Commands read from the repo's manifest — 1 month ago.

Skills (130)

• component-docs

  Create lean component documentation for OpenShift repositories

• generate-docs

  Generate and iteratively verify OpenShift component documentation, or review existing documentation, without relying on host-specific hooks or commands.

• review-docs

  Review agentic documentation by verifying local claims against source code and cross-repository claims against available authoritative resources. Use when checking generated or existing agent docs for factual accuracy, stale claims, broken references, or pre-PR readiness.

• update-platform-docs

  Update existing platform documentation with automatic gap detection in openshift/enhancements

• dashboard-templates

  Reference components for generating Kubernetes operator CRD dashboards

• generate-sbom

  Generate an AI SBOM declaration for a PR description. Use this skill when the user asks to generate an AI SBOM, create an ai-assisted block, fill out their AI assistance section, or prepare a PR description with AI provenance. Also use when the user says 'what skills did I use' or 'summarize my AI u

• analyze-usage

  Comprehensive analysis of BigQuery usage patterns, costs, and query performance

• ci-data-analyst

  Safely query and report on OpenShift CI prow job and test data in BigQuery with cost controls, dry-run validation, and local caching of results

• add-jira-triage-link

  Add a Component Readiness triage record link to a JIRA issue description

• analyze-disruption

  Analyze and compare disruption across one or more Prow CI job runs by examining interval data, audit logs, pod logs, and CPU metrics

• bulk-triage-regressions

  Use this skill for Component Readiness triage duty - holistically analyze and triage all untriaged regressions for a set of components in a view, clustering them into root-cause buckets

• detect-permafail

  Analyze consecutive job failures to determine if they represent a permafail pattern versus flaky failures

• diagnose-job-run-symptoms

  Explain which Sippy Symptoms and failure Labels apply to a Prow CI job run, in plain language, given only the Prow URL

• fetch-jira-issue

  Fetch JIRA issue details including status, assignee, comments, and progress classification

• fetch-job-run-summary

  Fetch a Prow job run summary from Sippy showing all failed tests grouped by SIG with error messages

• fetch-new-prs-in-payload

  Fetch pull requests that are new in a given OpenShift payload compared to the previous payload

• fetch-payloads

  Fetch recent release payloads from the OpenShift release controller

• fetch-prow-job-runs

  List Prow job runs from the Sippy API using its real filter syntax — find run IDs by job name, variant, result, or time window

• fetch-prowjob-json

  Fetch and return key data from a Prow job's prowjob.json artifact given a Prow job URL

• fetch-regression-details

  Fetch detailed information about a Component Readiness regression from the Sippy API

• fetch-related-triages

  Fetch existing triages and untriaged regressions related to a given regression

• fetch-releases

  Fetch available OpenShift releases from the Sippy API

• fetch-test-report

  Fetch an OpenShift CI test report by name to get pass rates, test ID, and Jira component from Sippy

• fetch-test-runs

  Fetch test runs from Sippy API including outputs for AI-based similarity analysis

• fetch-tide-pr-status

  Use when checking what's blocking a PR from merging in OpenShift CI — evaluates Tide merge requirements, required/forbidden labels, and required job statuses.

• list-symptoms

  List, search, and inspect Sippy Symptoms and Labels — known CI failure signatures — via the public Sippy API

• manage-labels

  Create, update, or delete Sippy job run Labels (the human-readable tags applied by Symptoms) via the authenticated Sippy API

• manage-symptoms

  Create, update, or delete Sippy Symptoms — known CI failure signatures that automatically label job runs — via the authenticated Sippy API

• oc-auth

  Helper skill to retrieve OAuth tokens from the correct OpenShift cluster context when multiple clusters are configured

• payload-analysis

  Analyze a payload snapshot to identify root causes of blocking job failures, score candidate PRs, and produce an HTML report with revert recommendations

• payload-autodl-json

  Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file

• payload-experimental-reverts

  Experimentally test medium-confidence payload candidates by opening draft revert PRs and triggering payload jobs

• payload-results-yaml

  State management for agentic payload triage actions — you must use this skill whenever reading or writing the payload results YAML file

• payload-snapshot

  Snapshot OpenShift payload data (release controller, PR diffs, comments, CI jobs, JUnit results, regression tracking) to a local directory for offline analysis

• prow-job-analysis

  Use this skill when debugging a failed Prow CI job.

• prow-job-analyze-resource

  Analyze Kubernetes resource lifecycle in Prow CI job artifacts by parsing audit logs and pod logs from GCS, generating interactive HTML reports with timelines

• reevaluate-job-runs

  Retroactively re-run Sippy Symptom detection on completed Prow CI job runs to apply or preview failure Labels

• revert-pr

  Git revert workflow and Revertomatic PR template for reverting merged PRs

• set-release-blocker

  Set the Release Blocker field on a JIRA issue

• stage-payload-reverts

  Create TRT JIRA bugs, open revert PRs, and trigger payload jobs for high-confidence revert candidates

• triage-regression

  Create or update a Component Readiness triage record linking regressions to a JIRA bug

• trigger-payload-job

  MUST be used whenever triggering payload testing on a PR. Do not post payload commands without following this skill — the command syntax is specific and other formats will be silently ignored by the bot.

• classify-review-comment

  Classify GitHub PR review comments by severity and topic. Use when the user wants to categorize, analyze, or understand patterns in code review feedback — whether for a single comment, a comment URL, or an entire pull request. Triggers on requests like 'classify this comment', 'categorize PR feedbac

• deep-review

  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.

• go-code-review

  Language-specific review guidance for Go code including idiomatic patterns, test conventions, and build commands

• hypershift-code-review

  Project-specific review profile for the openshift/hypershift repository — delegates to the repo's own agents and skills

• pre-commit-review

  Review staged and unstaged changes before committing. Use when asked for a pre-commit review, a code-quality review of the current diff, or when a solve workflow requests an independent review.

• analyze-cve

  Full Go CVE analysis workflow. Given a CVE identifier -- supplied directly, or resolved from a Jira ticket or JQL batch -- resolves and clones the affected repository, gathers vulnerability intelligence, analyzes codebase impact with govulncheck and call-graph reachability, generates a risk report,

• call-graph-analysis

  Perform definitive call graph analysis to prove whether vulnerable functions are reachable from program entry points

• codebase-impact-analysis

  Analyze a Go codebase to determine if it is impacted by a specific CVE using multiple verification methods and assign a risk level

• create-fix-pr

  Use when opening or updating a GitHub pull request after Phase 5 of `/compliance:analyze-cve` has applied and verified a CVE fix locally.

• cve-intelligence-gathering

  Gather comprehensive vulnerability information from multiple authoritative sources with fallback strategies

• image-repo-mapping

  Use when resolving which GitHub repository to clone for CVE analysis from a container image name in a Jira ticket summary, pscomponent label, or Downstream Component Name field.

• jira-cve-extraction

  Use when `/compliance:analyze-cve` is invoked with `--jira=` or `--jql=` and needs the CVE ID, image name, branch, and enriched ticket context from a Jira issue.

• remediation-planning

  Generate comprehensive remediation guidance including dependency updates, code changes, workarounds, and verification steps

• report-to-jira

  Use when posting a completed CVE analysis report or PR follow-up as a Jira comment on the source ticket from `/compliance:analyze-cve`.

• upgrade-console-sdk

  Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version.

• git-commit-format

  Apply conventional commit formatting rules. Use when generating commit messages or creating commits.

• suggest-reviewers

  Git blame analysis helper for the suggest-reviewers command

• check-pr-ci-status

  Check CI status on a GitHub PR and detect new failures. Use when monitoring a PR for CI regressions, deciding if CI failures need attention, or building a review-response loop.

• fetch-pr-comments

  Fetch new review comments from a GitHub PR, filtered to trusted users (org members + allowed bots). Use when monitoring a PR for feedback, checking for new review comments, or building a review-response workflow.

• upload-screenshot

  Upload screenshots or images to GitHub and get back embeddable URLs for PR comments and issues. Use this when you have taken a screenshot, captured a UI change, or have any image file that needs to be shared in a GitHub PR or issue.

• audit-release-go-version

  Audit the effective Go builder versions used by images in an OpenShift Container Platform release image or payload against a requested Go version. Use when the user asks which OCP release images were built with a different Go version, wants a concise payload Go-version audit, or needs Dockerfile bui

• fix-cve

  Patch a Go dependency to fix a CVE using the appropriate strategy based on Go version compatibility. Use when the user wants to fix a CVE by updating a Go module, replacing it with a patched fork, or applying a security patch across all go.mod files in a Go project. Triggers on: 'patch CVE', 'fix CV

• go-lint-fix

  Run golangci-lint and fix all reported issues. Use only when explicitly asked to fix lint issues in a Go project.

• go-lint

  Run golangci-lint to check Go code quality. Use when the user asks to lint, check for lint issues, or verify code quality in a Go project, or when linting is appropriate before committing Go code changes.

• native-fips

  Configure Go projects to use Go's native FIPS 140 module instead of openssl-based FIPS. Use when the user wants to enable FIPS compliance in a Go project, migrate from openssl-based FIPS to native Go FIPS, or when build configs contain GOEXPERIMENT=strictfipsruntime or openssl-based FIPS patterns. T

• triage-fixed-cves

  Triage Go stdlib CVEs against an OpenShift release image to determine which CVEs are fixed by the Go version each component was built with. Use when the user asks to triage Go stdlib CVEs against an OpenShift release image, check which Go CVEs are fixed in a release, or cross-reference Go vulnerabil

• hcp-create-agent

  Use this skill when you need to deploy HyperShift clusters on bare metal, edge environments, or disconnected infrastructures using pre-provisioned agents

• hcp-create-aws

  Use this skill when you need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials, IAM roles, and VPC configuration

• hcp-create-azure

  Use this skill when you need to deploy HyperShift clusters on Microsoft Azure with proper identity configuration and resource management

• hcp-create-kubevirt

  Use this skill when you need to deploy HyperShift clusters on existing Kubernetes clusters using KubeVirt virtualization

• hcp-create-openstack

  Use this skill when you need to deploy HyperShift clusters on OpenStack infrastructure with proper flavor selection and network configuration

• hcp-create-powervs

  Use this skill when you need to deploy HyperShift clusters on IBM Cloud PowerVS with proper processor configuration and resource management

• catch-me-up

  Gather and classify recent Jira activity to surface what needs attention

• categorize-activity-types

  Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools. Supports single-issue and batch modes. Use when the user wants to categorize or set activity types on Jira issues, or mentions activity types, work types, Sankey, or capacity allocation.

• create-release-note

  Detailed implementation guide for generating bug fix release notes from Jira and GitHub PRs

• create

  Create Jira issues — story, bug, epic, feature, initiative, task, risk, spike, or feature-request — with CNTRLPLANE, OCPBUGS, GCP, HyperShift, ARO, ROSA conventions and type-specific templates

• extract-prs

  Recursively extract GitHub Pull Request links from Jira issues

• generate-enhancement

  Generate OpenShift enhancement proposal markdown from Jira epic or feature content

• jira-conventions
• jira-doc-generator
• jira-issues-by-component
• jira-validate-blockers
• ready-to-solve
• status-analysis
• validate-bug
• must-gather-analyzer
• analyze-cve-repos
• query-open-cves
• report-findings
• node
• scripts
• k8s-ocp-olm-expert
• address-ci-failures
• address-review-pr
• address-review-precommit
• backport
• check-gates
• cherry-pick
• create-pr
• generate-test-plan
• has-review-work
• implement
• jira-solve
• qa-verify-console
• openshift-tls-profile
• generating-ovn-topology
• openshift-node-kernel
• ote-migration-workflow
• rds-analyzer-workflow
• setup-snowflake
• logs-analysis
• network-analysis
• ovs-db-analysis
• resource-analysis
• system-config-analysis
• analyze-regressions
• coderabbit-adoption
• coderabbit-inheritance-scanner-check
• coderabbit-inheritance-scanner-existing-pr
• coderabbit-inheritance-scanner-open-pr
• coderabbit-inheritance-scanner-search
• coderabbit-rules-from-pr-reviews
• get-release-dates
• list-components
• list-jiras
• list-regressions
• list-teams
• summarize-jiras

Similar plugins