
Shared engine for analyzing Jira issue activity and generating status summaries
Analyze a payload snapshot to identify root causes of blocking job failures, score candidate PRs, and produce an HTML report with revert recommendations
Snapshot OpenShift payload data (release controller, PR diffs, comments, CI jobs, JUnit results, regression tracking) to a local directory for offline analysis
Create TRT JIRA bugs, open revert PRs, and trigger payload jobs for high-confidence revert candidates
State management for agentic payload triage actions — you must use this skill whenever reading or writing the payload results YAML file
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
Query and deduplicate open CVE vulnerability issues from OCPBUGS for Node team components
Analyze a payload (rejected, accepted, or in-progress) with historical lookback to identify root causes of blocking job failures and produce an HTML report
Generate triage reports and post findings to Jira and Slack
Analyze CVE reachability against downstream repository forks at version-specific release branches
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
Detailed implementation guide for recursively analyzing Jira features and generating comprehensive documentation
Implementation guide for creating well-formed Jira user stories with acceptance criteria
Jira conventions and bug templates for the OCPBUGS project
Implementation guide for creating Jira tasks for technical and operational work
Implementation guide for creating Jira features representing strategic objectives and market problems
Implementation guide for creating Feature Requests in the RFE project
Detailed implementation guide for checking Jira issue readiness for /jira:solve
GCP HCP team-specific Jira requirements for creating issues in the GCP project (Hypershift on GKE)
Jira conventions for the CNTRLPLANE project used by OpenShift teams
Implementation guide for creating Jira epics with proper scope and parent linking
Recursively extract GitHub Pull Request links from Jira issues
Detailed implementation guide for generating bug fix release notes from Jira and GitHub PRs
HyperShift team-specific Jira requirements for component selection and conventions
Detailed implementation guide for validating proposed release blockers
Generate OpenShift enhancement proposal markdown from Jira epic or feature content
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.
Implementation guide for creating well-formed Jira bug reports
Fetch and filter human review comments from recent merged PRs in a GitHub repository
Generate comprehensive remediation guidance including dependency updates, code changes, workarounds, and verification steps
Fetch JIRA issue details including status, assignee, comments, and progress classification
Set the Release Blocker field on a JIRA issue
Perform definitive call graph analysis to prove whether vulnerable functions are reachable from program entry points
Project-specific review profile for the openshift/hypershift repository — delegates to the repo's own agents and skills
Analyze Kubernetes resource lifecycle in Prow CI job artifacts by parsing audit logs and pod logs from GCS, generating interactive HTML reports with timelines
Fetch detailed information about a Component Readiness regression from the Sippy API
Create or update a Component Readiness triage record linking regressions to a JIRA bug
Fetch existing triages and untriaged regressions related to a given regression
Fetch pull requests that are new in a given OpenShift payload compared to the previous payload
Comprehensive analysis of BigQuery usage patterns, costs, and query performance
Fetch a Prow job run summary from Sippy showing all failed tests grouped by SIG with error messages
Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version.
Use this skill when you need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials, IAM roles, and VPC configuration
Use this skill when you need to deploy HyperShift clusters on Microsoft Azure with proper identity configuration and resource management
Use this skill when you need to deploy HyperShift clusters on OpenStack infrastructure with proper flavor selection and network configuration
Detailed categorization logic for assigning JIRA tickets to activity type categories
Provides secure curl wrapper for the jira:issues-by-component command to prevent token exposure
Automated workflow for migrating OpenShift component repositories to OTE framework
End-to-end workflow from cluster data to deviation reports and optional Jira follow-up
Fetch OpenShift release dates and metadata from Sippy API
Analyzes LVMS must-gather data to diagnose storage issues
Query and return raw JIRA bug data for a specific project
Analyze system resource usage data from sosreport archives, extracting memory statistics, CPU load averages, disk space utilization, and process information from the sosreport directory structure to diagnose resource exhaustion, performance bottlenecks, and capacity issues
Grade component health based on regression triage metrics for OpenShift releases
Analyze Open vSwitch data from sosreport
Analyze system and application log data from sosreport archives, extracting error patterns, kernel panics, OOM events, service failures, and application crashes from journald logs and traditional log files within the sosreport directory structure to identify root causes of system failures and issues
Fetch and analyze component health regressions for OpenShift releases
Search for repos with .coderabbit.yaml files in the openshift GitHub org
Execute tests against generated mutants and analyze results to validate test suite quality for Kubernetes operators
List all OCPBUGS components, optionally filtered by team
Git revert workflow and Revertomatic PR template for reverting merged PRs
Add a Component Readiness triage record link to a JIRA issue description
Fetch an OpenShift CI test report by name to get pass rates, test ID, and Jira component from Sippy
Helper skill to retrieve OAuth tokens from the correct OpenShift cluster context when multiple clusters are configured
Search, list, and fetch artifacts from Prow CI job runs stored in GCS using the gcloud CLI
Use this skill when you need to deploy HyperShift clusters on existing Kubernetes clusters using KubeVirt virtualization
Use this skill when you need to deploy HyperShift clusters on bare metal, edge environments, or disconnected infrastructures using pre-provisioned agents
Git blame analysis helper for the suggest-reviewers command
Generate tuned manifests and evaluate node tuning snapshots
This skill should be used before any Snowflake command to verify MCP connectivity, guide users through access provisioning, and set the session context. Invoke this skill proactively whenever a command needs Snowflake data access.
Fetch and return key data from a Prow job's prowjob.json artifact given a Prow job URL
Analyze test code structure directly to provide coverage analysis
Analyze and compare disruption across one or more Prow CI job runs by examining interval data, audit logs, pod logs, and CPU metrics
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 usage'.
Analyze OpenShift bare metal installation failures in Prow CI jobs using dev-scripts artifacts. Use for jobs with "metal" in name, for debugging Metal3/Ironic provisioning, installation, or dev-scripts setup failures. You may also use the prow-job-analyze-install-failure skill with this one.
Analyze a Go codebase to determine if it is impacted by a specific CVE using multiple verification methods and assign a risk level
Use this skill when you need to deploy HyperShift clusters on IBM Cloud PowerVS with proper processor configuration and resource management
Run golangci-lint and fix all reported issues. Use only when explicitly asked to fix lint issues in a Go project.
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 CVE', 'replace grpc', 'update vulnerable dependency', 'security patch go module', or any mention of CVE + Go dependency replacement.
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.
Gather and classify recent Jira activity to surface what needs attention
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components. Use this skill when the user asks about cluster health, operator status, pod issues, node conditions, or wants diagnostic insights from must-gather data. Triggers: "analyze must-gather", "check cluster health", "operator status", "pod issues", "node status", "failing pods", "degraded operators", "cluster problems", "crashlooping", "network issues", "etcd health", "analyze clusteroperators", "analyze pods", "analyze nodes"
Use this skill to implement TLS security profiles for operators and workloads on OpenShift. Provides guidance on reading TLS config from APIServer CR and applying it to webhook/metrics servers, HTTP, and gRPC endpoints.
Use when the user asks about or needs help with Kubernetes (k8s), OpenShift (OCP), or Operator Lifecycle Manager (OLM) v0 or v1, including debugging resources, developing or troubleshooting operators, reviewing manifests or CRDs, explaining concepts, or investigating cluster issues.
Analyze network configuration data from sosreport archives, extracting interface configurations, routing tables, active connections, firewall rules (firewalld/iptables), and DNS settings from the sosreport directory structure to diagnose network connectivity and configuration issues
Generate code mutations for Kubernetes operator controllers to enable mutation testing. Applies operator-specific mutations to reconciliation logic, error handling, and API interactions.
Intelligently identify missing test coverage based on component type
Search for an existing fix PR on a repo before opening a new one
Report on CodeRabbit adoption across OpenShift org PRs
Analyze system configuration data from sosreport archives, extracting OS details, installed packages, systemd service status, SELinux/AppArmor policies, and kernel parameters from the sosreport directory structure to diagnose configuration-related system issues
List all teams from the team component mapping
Query and summarize JIRA bugs for a specific project with counts by component
Fork, sync, and open a fix PR to add inheritance: true to a repo's .coderabbit.yaml
Fetch recent release payloads from the OpenShift release controller
Fetch available OpenShift releases from the Sippy API
Fetch test runs from Sippy API including outputs for AI-based similarity analysis
Experimentally test medium-confidence payload candidates by opening draft revert PRs and triggering payload jobs
Reference components for generating Kubernetes operator CRD dashboards
Analyze failed Prow CI tests by inspecting test code, downloading artifacts, and optionally integrating must-gather cluster diagnostics for root cause analysis
Extract and decompress must-gather archives from Prow CI job artifacts, generating an interactive HTML file browser with filters
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.
Analyze OpenShift installation failures in Prow CI jobs by examining installer logs, log bundles, and sosreports. Use when CI job fails "install should succeed" tests at bootstrap, cluster creation or other stages.
Generates and displays OVN-Kubernetes network topology diagrams showing logical switches, routers, ports with IP/MAC addresses in Mermaid format
Inspect kernel-level networking configuration on OpenShift/Kubernetes nodes using oc debug
Gather comprehensive vulnerability information from multiple authoritative sources with fallback strategies
Language-specific review guidance for Go code including idiomatic patterns, test conventions, and build commands
Use when checking a repository's .coderabbit.yaml (or .coderabbit.yml) to determine whether inheritance: true is set
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 usage'.
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.
Run golangci-lint and fix all reported issues. Use only when explicitly asked to fix lint issues in a Go project.
Language-specific review guidance for Go code including idiomatic patterns, test conventions, and build commands
Analyze test code structure directly to provide coverage analysis
Intelligently identify missing test coverage based on component type
Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version.
Project-specific review profile for the openshift/hypershift repository — delegates to the repo's own agents and skills
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 feedback', 'what kind of review comments does this PR have', or 'break down comments by severity'.