52 skills published by openshift across 10 repositories. Together they weigh 109 825 tokens — that is what loading all of them at once would cost you in context.
52 skills 109 825 tokens total
Build and push control-plane-operator container image. Auto-applies when testing CPO changes that require deploying to a live cluster.
Build and push hypershift-operator container image. Auto-applies when testing HO changes that require deploying to a live cluster.
Interactively create CPO image overrides — resolves images, verifies fixes, edits overrides.yaml, and prepares a PR
Create a HyperShift HostedCluster on AWS for development and testing, with optional custom CPO/HO images.
Provides systematic debugging approaches for HyperShift hosted-cluster issues. Auto-applies when debugging cluster problems, investigating stuck deletions, or troubleshooting control plane issues.
Destroy a HyperShift HostedCluster and all associated AWS infrastructure (VPC, IAM, Route53, etc.).
Provides the ability to run and iterate on HyperShift e2e tests. Auto-applies when implementing features that require e2e validation, fixing e2e test failures, or working on tasks that need live cluster testing.
Apply HyperShift conventional commit formatting rules. Use when generating commit messages or creating commits.
Create development environments with git worktrees, branches, commits, and push to remote. Auto-applies for git workflow tasks.
Install HyperShift Operator with private AWS and external-dns settings.
Accesses archived Konflux PipelineRuns, TaskRuns, and pod logs via KubeArchive. Auto-applies when checking Konflux PipelineRun results, investigating enterprise contract failures, or retrieving logs from completed Konflux CI runs.
Assess whether an AWS VPC or infra set from HyperShift CI is safe to delete. Use when the user pastes cleanleaked output and asks 'can I delete this?', 'is this safe to remove?', 'triage this infra', asks about a LEAKED or UNCERTAIN verdict, provides a VPC ID or infraID and wants to know if it's orphaned, or says 'check this VPC'. Also use when the user asks 'should I delete this?' about any AWS resource in the HyperShift CI account.
Validates that CPO override images in a PR actually contain the PRs they claim to include
Comprehensive bug workflow for OpenShift Console - investigates issues, creates JIRA bug reports following Red Hat standards, offers branch creation, and proposes fixes with regression tests.
Debug and fix failing Playwright e2e tests with MCP-assisted diagnosis. Use when user says "playwright test failing", "fix e2e test", "debug spec", or provides a failing .spec.ts file, e2e directory, or Playwright tag.
Generate React Testing Library tests following OCP Console best practices
Reviews user-facing microcopy against content design guidelines and provides clear, actionable recommendations.
Migrate a Cypress test file (.cy.ts) or Gherkin feature file (.feature) to Playwright following Console's architecture. This is the ONLY skill for Cypress-to-Playwright conversion work, you can perform full migration, analysis-only (--analyze), or dry-run (--dry-run) modes.
Review changes to the OpenShift Console plugin API for compliance with contribution guidelines, styleguide, and proper documentation in changelogs. Provides a detailed report of findings and compliance score.
Comprehensive local code review using both Claude AI and CodeRabbit AI before pushing changes to GitHub. This command analyzes your local changes and provides actionable feedback without posting anything to GitHub.
>- Automated QA verification for OpenShift Console PRs. Builds and runs the console on both main and the PR branch, captures before/after screenshots and GIFs via Playwright MCP, then posts a side-by-side comparison as a GitHub PR comment. Use when the user asks to verify a PR, QA changes, capture visual proof, or show before/after evidence.
Audit all Claude Code skills for stale references, broken paths, and deprecated tool names
Expert package update assistant for OpenShift Console. Update packages safely with automated testing, building, and fixing.
>- Add a new step-registry step (ref YAML + commands.sh) in openshift/release. Use when creating a new CI step, atomic test action, or reusable ref component. Run step-finder first to avoid duplicates.
>- Check AKS Kubernetes version support status using the official AKS release status API and compare against versions configured in CI config files. Use whenever someone asks about AKS K8s version support, EOL dates, deprecation, or whether the configured AKS version is still GA. Also use when planning AKS K8s version upgrades — run this before using rhdh-aks-tests to make changes.
>- List AKS test entries in RHDH ci-operator config files and update the AKS Kubernetes version per branch. Use when listing e2e-aks tests, changing MAPT_KUBERNETES_VERSION for AKS, or checking which AKS K8s version each release branch uses.
>- Use when decommissioning an end-of-life RHDH release branch by removing CI config, generated Prow jobs, and branch protection from the openshift/release repository
>- Check EKS Kubernetes version support status using the official AWS EKS docs source and compare against versions configured in CI config files. Use whenever someone asks about EKS K8s version support, EOL dates, or whether the configured EKS version is still in standard support. Also use when planning EKS K8s version upgrades — run this before using rhdh-eks-tests to make changes.
>- List EKS test entries in RHDH ci-operator config files and update the EKS Kubernetes version per branch. Use when listing e2e-eks tests, changing MAPT_KUBERNETES_VERSION for EKS, or checking which EKS K8s version each release branch uses.
>- Check GKE Kubernetes version support status using the endoflife.date API (auto-scraped from Google's GKE release schedule). Use whenever someone asks about GKE K8s version support, EOL dates, or whether the current GKE cluster version is still supported. GKE uses a long-running static cluster whose version is not managed in CI config.
>- List GKE test entries in RHDH ci-operator config files. Use when listing e2e-gke tests or checking which branches have GKE test entries. Unlike AKS/EKS, GKE uses a pre-existing static cluster — version upgrades are performed via the GCP Console.
>- Analyze RHDH OCP version coverage by cross-referencing cluster pools and CI test configs against both RHDH and OCP lifecycle APIs to find gaps, stale configurations, and compatibility mismatches
>- Check which OCP versions are supported by active RHDH releases and which are end-of-life, using the Red Hat Product Life Cycles API for both RHDH and OCP lifecycle data including EUS phases. Supports OCP 4.x and future 5.x+
>- List existing RHDH OCP Hive ClusterPool configurations and generate new pool YAML for a target OCP version, with imageSetRef aligned from other pools in the openshift/release repository. Covers OCP pools only, not K8s platforms
>- List, generate, add, and remove OCP-versioned test entries (e2e-ocp-*) in RHDH ci-operator config files. Covers only OCP cluster-claim tests, not K8s platform tests (AKS, EKS, GKE, OSD)
>- Search openshift/release step-registry for existing steps, workflows, and chains before creating new CI components. Use when adding tests, jobs, or step-registry entries, or when asked to find reusable pre/test/post components.
The InternalReleaseImage controller manages the IRI resource lifecycle, generates MachineConfigs for the IRI registry, updates status by aggregating from MachineConfigNodes, and handles deletion. Use when reviewing controller implementation or validating behaviors.
Describes the acceptance criteria and BDD tests to be used for new/existing features of the InternalReleaseImage MachineConfigDaemon manager. The manager implements the NoRegistryClusterInstall main feature for the part related to manage/monitor a single control plane node
Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.
Analyze all past sessions for this project and extract knowledge worth persisting to AGENTS.md, .claude/agents/, or memory. Deep analysis of full session history.
Review the current session and extract knowledge worth persisting to AGENTS.md, .claude/agents/, or memory. Use at the end of a session to capture what was learned.
Build and code-generate assisted-service using skipper with podman. Use when running make targets, building the service, regenerating code from swagger or CRDs, running linters, or any containerized development task. Also use when the user encounters build errors, needs to set up their development environment, or asks about how to run tests.
Use when writing non-subsystem tests in assisted-service.
Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror
Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps
Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
Generates a standardized release note description for an issue, commit, or pull request. Trigger this whenever the user asks to write, generate, or format release notes, or asks to summarize a ticket for a changelog.
Run strict OpenShift API review workflow for PR changes or local changes
Cross-check AWS-facing code and docs against official ROSA and AWS references before changing behavior.
Add or edit Cobra commands in openshift/rosa while keeping command wiring thin and package logic aligned with repo structure.
Keep CLI docs, structure tests, and user-facing guidance in sync when commands or workflow docs change.
Choose the right local verification steps before claiming a ROSA change is complete.