openshift-eng

Generate a comprehensive manual testing guide from a Jira issue, GitHub PR URLs, or both. Use when the user wants test steps, a QE test plan, or a testing guide for code changes.

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

Generate triage reports and post findings to Jira and Slack

Query and deduplicate open CVE vulnerability issues from OCPBUGS for Node team components

Check whether a Jira issue is well-groomed and ready for /jira:solve

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

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

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

Surface your daily task list — QA-ready tickets, sprint backlog, carry-over items, open PRs, RHEL verification queue, and quarterly reminders. Use at the start of your day to see what needs attention.

Show detailed info about a specific TODO task — its tracked links, notes, and live Jira/PR status. Use when the user asks about a task, wants context to resume work on it, or asks what's needed to finish a ticket. Not for listing all tasks (read the TODO file directly or use edge-ic:sprint-status for sprint-wide views)

End-of-week automation - review active work and prepare next week's TODO

Run the full Prow CI release testing workflow — create PR, trigger jobs, check status, merge PR, download and upload artifacts

Generate interactive PCP performance dashboard from a Prow job URL

Download Prow job artifacts, identify root cause of failure, and produce a structured error report

Download Prow job artifacts, identify root cause of failure, and produce a structured error report

Validate Konflux bootc advisory promotion for QE sign-off — verify advisory YAML, catalog presence, shipment MR, and commit provenance

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

Grade component health based on regression triage metrics for OpenShift releases

Use when checking a repository's .coderabbit.yaml (or .coderabbit.yml) to determine whether inheritance: true is set

Fork, sync, and open a fix PR to add inheritance: true to a repo's .coderabbit.yaml

Fetch and analyze component health regressions for OpenShift releases

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

Analyze a payload (rejected, accepted, or in-progress) with historical lookback to identify root causes of blocking job failures and produce an HTML report

Report on CodeRabbit adoption across OpenShift org PRs

Analyze OpenShift operator API changes to predict regressions, breaking changes, and backward compatibility issues

Analyze RFEs and generate EPIC, user stories, and outcomes breakdown

Generate e2e test artifacts for any OpenShift operator based on repository discovery and git diff analysis

Scaffold a new MCP tool with handler, registration, and test

Build, tag, and publish a new release with cross-compiled binaries and GitHub release

Download Prow CI job artifacts for analysis. Understands Prow artifact structure, so is more efficient than manual fetching. Use when user provides a prow URL, asks about CI job results (pass or fail), mentions a PR's test results (pass or fail), or wants to examine CI logs.