ci

Plugin ci from marketplace ai-helpers in openshift-eng/ai-helpers. Commands read from the repo's manifest — today.

Skills (36)

• add-jira-triage-link

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

• analyze-disruption

  Use when analyzing disruption from a DisruptionRegression alert, a Grafana disruption dashboard URL, or 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.

• generate-okd-ci-operator-configs

  Use when you need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data. Replicates the logic of doozer's `images:okd prs open` command as a standalone tool.

• 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

• prow-job-prometheus

  Use when you need in-cluster Prometheus metrics from a Prow CI job run — apiserver in-flight requests, etcd disk latency, node CPU/memory/disk, per-pod usage, restarts — by downloading the run's Prometheus snapshot, repairing it, and querying it locally with PromQL

• 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.

Slash commands (20)

• /ci:add-debug-wait

  Add a wait step to a CI workflow for debugging test failures

• /ci:analyze-pr-reverts

  Analyze recent PR reverts to identify patterns and recommend preventive measures

• /ci:analyze-prow-job-resource

  Analyze Kubernetes resource lifecycle in Prow job artifacts

• /ci:analyze-regression

  Analyze details about a Component Readiness regression and suggest next steps

• /ci:check-if-jira-regression-is-ongoing

  Check if the regression described in a Jira bug is still ongoing or has resolved

• /ci:continue-session

  Download and continue a Claude session from a Prow CI job's artifacts

• /ci:detect-permafail

  Detect permafail patterns in consecutive job failures

• /ci:extract-kubeconfig

  Extract kubeconfig from a running CI job in a PR

• /ci:fetch-payloads

  Fetch recent release payloads from the OpenShift release controller

• /ci:fetch-test-report

  Fetch a test report from Sippy showing pass rates, test ID, and Jira component

• /ci:list-step

  List the step for the given workflow or chain name

• /ci:list-unstable-tests

  List unstable tests with pass rate below 95%

• /ci:payload-experiment

  Open draft revert PRs for medium-confidence payload candidates and trigger payload jobs to experimentally determine which PR is causing failures

• /ci:payload-revert

  Stage reverts for high-confidence payload candidates identified by payload-analysis

• /ci:query-job-status

  Query the status of a gangway job execution by ID

• /ci:query-test-result

  Query test results from Sippy by version and test keywords

• /ci:revert-pr

  Revert a merged PR that is breaking CI or nightly payloads

• /ci:trigger-periodic

  Trigger a periodic gangway job with optional environment variable overrides

• /ci:trigger-postsubmit

  Trigger a postsubmit gangway job with repository refs

• /ci:trigger-presubmit

  Trigger a presubmit gangway job (typically use GitHub Prow commands instead)

Subagents (2)

• step-registry-analyzer

  Use this agent when you need to understand and list OpenShift CI components including workflows, chains, and refs in a hierarchical structure.

• test-porter

  Automated Ginkgo e2e test porting agent. Ports tests from openshift-tests-private to openshift/origin, creates PRs, monitors CI, responds to review feedback, pushes fixes, and escalates to humans when needed. Use this agent for any task related to porting tests between these repos.

MCP servers (1)

• ship-status

  connects to: https://mcp.ship-status.ci.openshift.org/mcp

Similar plugins