agent-skills

Use when asked to assess OpenShift cluster health, explain degraded status, troubleshoot control-plane issues, or produce a health report — including degraded operators, node issues, etcd problems, auth failures, ingress errors, certificate expiry, upgrade readiness, post-maintenance validation, pending pods, CrashLoopBackOff, scheduling failures, quota exhaustion, or OOMKilled pods.

Use when discovering, planning, installing, validating, hardening, upgrading, migrating, backing up, restoring, maintaining, uninstalling, or troubleshooting Longhorn on OpenShift/OKD — including Single Node OpenShift, dedicated disk preparation, V1 filesystem data disks, V2 block/SPDK data engine, oauth-proxy handling, SCC/MachineConfig workflows, StorageClass defaulting, and lifecycle safety.

Use when planning, installing, configuring, validating, upgrading, expanding, shrinking, backing up, restoring, maintaining, or troubleshooting LVM Storage (LVMS) on OpenShift/OKD — including Single Node OpenShift, multi-node clusters, volume group provisioning, thin pool configuration, TopoLVM CSI filesystem and raw block volumes, volume group expansion, disk management, StorageClass defaulting, and lifecycle safety.

Use when planning, installing, configuring, validating, upgrading, expanding, shrinking, backing up, restoring, maintaining, or troubleshooting Red Hat OpenShift Data Foundation (ODF) on OpenShift/OKD — including Single Node OpenShift, multi-node clusters, internal mode with Local Storage Operator disks, StorageCluster sizing, ceph-rbd block, cephfs shared filesystem, Multicloud Object Gateway (MCG/NooBaa) and RGW object storage, OLM operator lifecycle, and default StorageClass safety.

Use when planning, installing, configuring, validating, upgrading, expanding, shrinking, backing up, restoring, maintaining, or troubleshooting Rook Ceph on OpenShift/OKD — including Single Node OpenShift, multi-node clusters, dedicated block disks for OSDs, CephBlockPool RBD, CephFS filesystem, CephObjectStore RGW/S3, host networking, device discovery, stretch clusters, PG/PGP tuning, and operator lifecycle safety.

Use when the user asks to simplify, clean up, refactor, tidy, reduce complexity, improve readability, or review code quality in any programming language — including direct rewrites, refactor reviews, readability passes, and targeted cleanup before a PR.

Use when the user mentions presentations, slide decks, pitch coaching, talk structure, presentation openings, slide audits, making ideas stick, empowerment promises, the Star framework, contribution slides, or asks to improve how they present, pitch, or teach an audience — even without naming Winston.

Use when users ask about available OpenShift versions, latest patch versions, upgrade paths, ROSA/OSD versions, channel-specific releases, end-of-life dates, or phrases like "what OCP versions exist", "what can I upgrade to", "latest OCP patch", or "is 4.x still supported".

Use when the request involves quality review, risk-based test planning, bug reproduction, regression analysis before release, API or contract verification, or exploratory testing strategy and evidence reporting.

Use when reviewing production readiness, resilience, failure modes, or reliability of code, services, or system designs. Trigger for requests about error handling, retries, timeouts, circuit breakers, graceful degradation, observability, DR/RPO/RTO, abuse resilience, quota exhaustion, production architecture trade-offs affecting resilience, operability, cost, or failure modes, complexity tax analysis, or AI-generated code risk checks.

Use when a decision sounds reasonable but still needs pressure-testing before agreement, especially for scope, architecture, sequencing, or irreversible product trade-offs.

Use when you need to display GitHub PR review comments in the code review UI, or inspect review feedback on the current branch before deciding how to respond.