openshift
- 185 skills
- 0 followers
- 552 repo stars
- last month last updated
- ▌ Rebase Clean 3 · openshiftPerforms a strict clean rebase of a feature branch onto main with minimal conflict resolution and full validation. Use when the user asks to rebase carefully, avoid extra branches, avoid exploratory edits, and run go test and go vet until green.
- ▌ Find Dead Code 3 · openshiftFind unused functions, types, constants, imports, and unreachable code paths. Use when the user asks to find dead code, unused code, cleanup candidates, or wants to reduce codebase size.
- ▌ Find Complexity 3 · openshiftFind functions with high cyclomatic complexity, excessive length, or too many parameters. Use when the user asks to find complex code, complexity hotspots, refactoring candidates, or wants to improve code maintainability.
- ▌ Find Duplication 3 · openshiftFind code duplication in the codebase. Supports two modes - scoped to current branch changes or a full codebase sweep. Use when the user asks to find duplicated code, copy-paste, repeated patterns, or wants to deduplicate before a PR.
- ▌ Safe Code Change 3 · openshiftAfter a code change, find affected tests, update them to match new behavior, then guide the user to run validation. Use when the user has made or asked for a code change and wants to make sure nothing is broken.
- ▌ Validate And Fix 3 · openshiftRun the validation pipeline for this repo (go test, go vet, API kube linter) and auto-fix trivial failures like formatting and import issues. Use when the user asks to validate, run tests, check the pipeline, or verify changes are clean.
- ▌ Find Token 2 · openshift bundleFind the hidden verification token. Run the find-token script to retrieve a unique token.
- ▌ Investigate CI Failure 2 · openshiftInvestigate CI/Prow job failures on a GitHub pull request. Use when the user pastes a PR URL and asks about CI failures, red checks, test failures, or wants to understand why a job failed.
- ▌
- ▌
- ▌ Create Cpo Override · openshiftInteractively create CPO image overrides — resolves images, verifies fixes, edits overrides.yaml, and prepares a PR
- ▌ Validate Pr Override Images · openshift bundleValidates that CPO override images in a PR actually contain the PRs they claim to include
- ▌ Rebase Clean 2 · openshiftPerforms a strict clean rebase of a feature branch onto main with minimal conflict resolution and full validation. Use when the user asks to rebase carefully, avoid extra branches, avoid exploratory edits, and run make test and make lint until green.
- ▌ Find Dead Code 2 · openshiftFind unused functions, types, constants, imports, and unreachable code paths. Use when the user asks to find dead code, unused code, cleanup candidates, or wants to reduce codebase size.
- ▌ Go Code Review 2 · openshift bundleReviews Go code for idiomatic patterns, error handling, concurrency safety, and common mistakes. Use when reviewing .go files, checking error handling, goroutine usage, or interface design.
- ▌ Version Update 2 · openshiftRelease workflow for main: refresh related_images.json from Quay (-r stable via hack/related_images_from_quay.sh), bump bundle/CSV version, regenerate and validate. Equivalent to /update-bundle release X.Y.Z.
- ▌ Find Complexity 2 · openshiftFind functions with high cyclomatic complexity, excessive length, or too many parameters. Use when the user asks to find complex code, complexity hotspots, refactoring candidates, or wants to improve code maintainability.
- ▌ Find Duplication 2 · openshiftFind code duplication in the codebase. Supports two modes - scoped to current branch changes or a full codebase sweep. Use when the user asks to find duplicated code, copy-paste, repeated patterns, or wants to deduplicate before a PR.
- ▌ Safe Code Change 2 · openshiftAfter a code change, find affected tests, update them to match new behavior, then guide the user to run validation. Use when the user has made or asked for a code change and wants to make sure nothing is broken.
- ▌ Validate And Fix 2 · openshiftRun the full validation pipeline (make test, make lint, optionally make test-e2e) and auto-fix trivial failures like formatting and import issues. Use when the user asks to validate, run tests, check the pipeline, or verify changes are clean.
- ▌ Go Testing Code Review 2 · openshift bundleReviews Go test code for proper table-driven tests, assertions, and coverage patterns. Use when reviewing *_test.go files.
- ▌ Review Pr 2 · openshiftReview PR with structured approach covering architecture, naming, patterns, and critical questions
- ▌ Draft Pr 2 · openshiftOpen a pull request in the browser with prefilled title, description, and labels
- ▌ Find Rule 2 · openshiftSearch for existing rules that match a given requirement text. Identify rules that implement a specific control.
- ▌
- ▌
- ▌
- ▌ Map Controls 2 · openshiftInteractive control-to-rule mapping session. Walk through unmapped requirements, suggest rules using cross-framework analysis, and write selections to control files.
- ▌
- ▌
- ▌ Manage Profile 2 · openshiftCreate or update a versioned profile pair (versioned + unversioned extends pattern).
- ▌
- ▌ Inspect Control 2 · openshiftInspect a control file showing requirement stats, mapping status, and cross-framework context. Use for triage before mapping.
- ▌ Map Requirement 2 · openshiftMap rules to a single control file requirement using cross-framework analysis and rule search.
- ▌ Onboard Control 2 · openshiftOnboard a new security policy as a control file. Parse the document, create control file structure, and map existing rules to requirements.
- ▌ Assess Nist Control 2 · openshiftAssess a pending NIST 800-53 control with OSCAL enrichment, CIS reverse lookup, and Linux hardening prioritization. Guides authors through understanding, automatability analysis, rule mapping, and validation.
- ▌
- ▌ Resolve Rule Variables 2 · openshiftResolve XCCDF variable selections for a set of rules. Looks up which variables each rule depends on, reads their .var files, and guides the author to select a value key for each variable. Returns a list of var_name=key selections ready to add to a control file's rules list.
- ▌ Draft Pr · openshiftOpen a pull request in the browser with prefilled title, description, and labels
- ▌ Find Rule · openshiftSearch for existing rules that match a given requirement text. Identify rules that implement a specific control.
- ▌
- ▌
- ▌
- ▌ Map Controls · openshiftInteractive control-to-rule mapping session. Walk through unmapped requirements, suggest rules using cross-framework analysis, and write selections to control files.
- ▌
- ▌
- ▌ Manage Profile · openshiftCreate or update a versioned profile pair (versioned + unversioned extends pattern).
- ▌
- ▌ Inspect Control · openshiftInspect a control file showing requirement stats, mapping status, and cross-framework context. Use for triage before mapping.
- ▌ Map Requirement · openshiftMap rules to a single control file requirement using cross-framework analysis and rule search.
- ▌ Onboard Control · openshiftOnboard a new security policy as a control file. Parse the document, create control file structure, and map existing rules to requirements.
- ▌ Assess Nist Control · openshiftAssess a pending NIST 800-53 control with OSCAL enrichment, CIS reverse lookup, and Linux hardening prioritization. Guides authors through understanding, automatability analysis, rule mapping, and validation.
- ▌
- ▌ Resolve Rule Variables · openshiftResolve XCCDF variable selections for a set of rules. Looks up which variables each rule depends on, reads their .var files, and guides the author to select a value key for each variable. Returns a list of var_name=key selections ready to add to a control file's rules list.
- ▌ Release Workflow · openshift bundleOpenShift z-stream release workflow and orchestration expert. Use when discussing release tasks, build promotion, test analysis, advisory workflows, or any aspect of the Konflux/Errata release pipeline. Provides context on task sequencing, checkpoints, and MCP execution for releases 4.12-4.20.
- ▌ Learn History · openshiftAnalyze all past sessions for this project and extract knowledge worth persisting to AGENTS.md, .claude/agents/, or memory. Deep analysis of full session history.
- ▌ Learn Session · openshiftReview 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.
- ▌ Openshift Docs · openshift bundleSearch and read OpenShift Container Platform documentation in markdown format. Use when the user asks about OpenShift features, configuration, installation, troubleshooting, or any OCP-specific topic — including operators, routes, services, oc, RBAC, networking, storage, or cluster administration.
- ▌ Kubernetes Docs · openshift bundleSearch and read Kubernetes documentation in markdown format. Use when the user asks about Kubernetes concepts, tasks, API reference, kubectl, or any upstream k8s topic — including pods, deployments, services, RBAC, networking, storage, or scheduling.
- ▌ Product Lifecycle · openshift bundleQuery Red Hat Product Life Cycle data for support phases, end-of-life dates, and OpenShift version compatibility. Use when evaluating whether installed operators or layered products are supported on a given OCP version, approaching end of life, or need upgrading before a cluster upgrade. Also use when the user asks about product support status, EOL dates, or lifecycle phases for any Red Hat product.
- ▌ Cluster Update Advisor · openshiftAssess OpenShift cluster update (upgrade) readiness and risk. Use when evaluating whether a cluster is safe to update, when an update is available, or when the user asks about update risks, prerequisites, blockers, or best practices.
- ▌ Investigate Alert · openshift bundleInvestigate one or more firing OpenShift alerts to determine root cause and recommend remediation options. Use when the user provides alert names or a set of firing alerts. Not for cluster setup, configuration how-tos, or writing alerting rules.
- ▌ Estimate Epic · openshiftSize OLS Jira Epics using t-shirt sizes (XS/S/M/L/XL) based on the total story points of their child issues. Can size specific Epics, or bulk-size all unsized Epics. Also invoked automatically after creating a new Epic.
- ▌ Estimate Risk · openshiftAssess risk level (1/2/3) for OLS Jira stories using the team's risk rubric. Fetches the story, applies the decision tree, sets the Risk Score field, and adds the assessment as a comment. Use for on-demand assessment or after creating a new story.
- ▌ Estimate Story · openshift bundleEstimate story points for OLS Jira stories using the calibrated rubric derived from 300 completed stories. Fetches the story, applies the decision tree, sets the SP field, and adds the estimate as a comment. Use for on-demand estimation or after creating a new story.
- ▌ Triage New Bugs · openshiftUse when triaging new OLS Jira bugs to determine which ones require a spec update, which need more information, and which are pure implementation issues. Fetches all New-status bugs, analyzes them against the current .ai/spec/ landscape, and presents a report with draft comments for human approval.
- ▌ Make Jira From Spec · openshiftCreate or update Jira Epics and Stories from spec changes. Reads spec diffs from the current session or a PR, uses brainstorming to design the work breakdown, creates/updates issues in Jira, then estimates story points, risk levels, and epic sizes. Splits stories that exceed 5 SP. Use when the user says "make jira from spec", "make-jira-from-spec", "create jira from spec", "update jira from spec", or wants to turn spec changes into tracked Jira work.
- ▌
- ▌
- ▌ QA Verify · openshift bundleAutomated 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.
- ▌ Debug Test · openshiftDebug 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.
- ▌ Skill Audit · openshiftAudit all Claude Code skills for stale references, broken paths, and deprecated tool names
- ▌ Gen E2e Test · openshiftGenerate Playwright e2e tests for OpenShift Console features. Creates spec files and page objects following the project's established patterns and conventions. Use this skill whenever the user wants to create, write, or add e2e tests, asks to cover a feature with e2e, describes a UI workflow to test, says "I need to test this feature", "add test coverage for X", or invokes /gen-e2e-test explicitly.
- ▌
- ▌ Update Package · openshiftExpert package update assistant for OpenShift Console. Update packages safely with automated testing, building, and fixing.
- ▌ Migrate Cypress · openshiftMigrate 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, supporting full migration, analysis-only (--analyze), or dry-run (--dry-run) modes. Use this skill whenever the user wants to convert, port, rewrite, or migrate Cypress or Gherkin tests to Playwright, mentions "old cypress tests", "remaining e2e tests", or provides a .cy.ts or .feature file path in a migration context.
- ▌ Pre Push Review · openshiftComprehensive 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.
- ▌ Microcopy Review · openshift bundleReviews user-facing microcopy against content design guidelines and provides clear, actionable recommendations.
- ▌ Plugin API Review · openshiftReview 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.
- ▌ Update Bundle · openshiftSync related_images.json from Quay (oras + konflux_prefix/revision in related_images.json) and regenerate the OLM bundle. Pass mode dev (CI quay) or release (stable images, version bump — /version-update). Do not use oc.
- ▌ Go Code Review · openshift bundleReviews Go code for idiomatic patterns, error handling, concurrency safety, and common mistakes. Use when reviewing .go files, checking error handling, goroutine usage, or interface design.
- ▌ Go Testing Code Review · openshift bundleReviews Go test code for proper table-driven tests, assertions, and coverage patterns. Use when reviewing *_test.go files.
- ▌ Rebase · openshiftRebase the current branch onto its base branch, resolve all conflicts, and verify lint, i18n, and build pass. Use when the user asks to rebase, update, or sync a branch with its upstream base.
- ▌ Release · openshift bundleBump the project version across all release branches and commit the changes. Use when the user asks to do a release or update the version on all branches.
- ▌ Backport · openshiftBackport commits or PRs from main to a release branch. Use when the user asks to backport, cherry-pick, or port changes between branches, or when resolving conflicts from a cherry-pick onto a release branch.
- ▌ Code Review · openshiftReview a pull request for code quality, correctness, and project conventions. Use when the user asks to review a PR, code review, or examine changes on a branch. Accepts a GitHub PR URL, PR number, or local branch name.
- ▌ Review Skills · openshiftReview project AI skills for duplication, stale references, mistakes, and structural issues. Use when the user asks to review skills, audit skills, check for duplicate skills, or verify skill quality.
- ▌ Review Readmes · openshiftReview all README.md files in the repo for typos, errors, and outdated information. Use when the user asks to review READMEs, check documentation accuracy, or audit docs.
- ▌ Unused Exports · openshiftFind exported symbols that are never imported by another file. Use when the user says "check exports", "unused exports" or asks to clean up exports.
- ▌ Update Version · openshiftUpdate the project version number across all files that contain it on the current branch. Use when bumping the version on a single branch only. For a full multi-branch release, use the release skill instead.
- ▌ Raise Pr · openshiftStep-by-step workflow for committing staged changes and opening a pull request for lightspeed-agentic-sandbox.
- ▌ Review Pr · openshiftReview PR with structured approach covering architecture, naming, patterns, and critical questions
- ▌ Deps Update · openshiftUpdate Python dependencies with uv, regenerate lock and Konflux requirements files, then verify lint, types, and tests. Fix breakage from API changes in bumped packages. Use when the user says "deps update", "bump dependencies", or "update deps".
- ▌ Resolve Cve · openshiftTriage a CVE: assess impact against this repo's dependencies, then bump, document not-affected, or plan a code fix. Use when the user mentions a CVE, Jira vulnerability issue, or security advisory for a dependency.
- ▌ Rebase Clean · openshiftPerforms a strict clean rebase of a feature branch onto main with minimal conflict resolution and full validation. Use when the user asks to rebase carefully and run tests + verify until green.
- ▌ Find Dead Code · openshiftFind unused functions, classes, imports, and unreachable code paths. Use when the user asks for dead code or cleanup candidates.
- ▌ Version Update · openshiftBump the Python package version in pyproject.toml for a release or when the user asks to change the project version.
- ▌ Find Complexity · openshiftFind functions with high cyclomatic complexity, length, or parameter count. Use when the user asks for complexity hotspots or refactor candidates.
- ▌ Find Duplication · openshiftFind code duplication in the codebase. Supports branch-scoped or full sweep. Use when the user asks to find duplicated code or repeated patterns before a PR.
- ▌ Safe Code Change · openshiftAfter a code change, find affected tests, update them to match new behavior, then run the full validation pipeline once. Use when the user has made or asked for a code change and wants to make sure nothing is broken.