tomazb

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

Template skill that summarizes the current branch's changes. Use as a starting point for authoring new first-party skills.

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

Thermo-nuclear code-quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo) scoped to the diff. Launches the thermo-nuclear-code-quality-review-subagent custom agent on the collected diff.

Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.

Thermo-nuclear branch audit (bugs, breaking changes, security, devex, feature-flag leaks) scoped to the diff. Launches the thermo-nuclear-review-subagent custom agent on the collected diff.

Run both Thermos review passes, then synthesize a single deduplicated report. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.

Safely simplify a Python module by extracting long methods, consolidating boilerplate, and applying existing patterns. Usage - /refactor-simplify modules/finalization.py or /refactor-simplify --review modules/finalization.py

Bump version across all project files (Python, Bash, Container, Helm, README, CHANGELOG). Usage - /release 1.6.0

Use for "rubber duck", "/rubber-duck", "second opinion", "critique this plan", "critique these changes", "get a critique", or when the consult-rubber-duck rule says to seek a constructive second opinion. Spawns a read-only critic on a contrasting model family; does not edit files.