This document lists all available Claude Code plugins and their commands in the ai-helpers repository.
- Agendas
- Bigquery
- Ci
- Code Review
- Compliance
- Container Image
- Doc
- Etcd
- Git
- Golang
- Gwapi
- Hcp
- Hello World
- Jira
- Lvms
- Must Gather
- Node
- Node Tuning
- Olm
- Olm Team
- Openshift
- Origin
- Ote Migration
- Session
- Sosreport
- Teams
- Test Coverage
- Testing
- Utils
- Workspaces
- Yaml
A plugin to create various meeting agendas
Commands:
/agendas:outcome-refinement- Analyze the list of JIRA outcome issues to prepare an outcome refinement meeting agenda.
See plugins/agendas/README.md for detailed documentation.
BigQuery cost analysis and optimization utilities
Commands:
/bigquery:analyze-usage<project-id> <timeframe>- Analyze BigQuery usage and costs for a project
See plugins/bigquery/README.md for detailed documentation.
Tools for working with OpenShift CI and analyzing Prow job results
Commands:
/ci:add-debug-wait<workflow-or-job-name> [timeout]- Add a wait step to a CI workflow for debugging test failures/ci:analyze-payload<payload-tag> [--lookback N]- Analyze a rejected or in-progress payload with historical lookback to identify root causes of blocking job failures/ci:analyze-pr-reverts[limit]- Analyze recent PR reverts to identify patterns and recommend preventive measures/ci:analyze-prow-job-install-failure<prowjob-url>- Analyze OpenShift installation failures in Prow CI jobs/ci:analyze-prow-job-resourceprowjob-url resource-name- Analyze Kubernetes resource lifecycle in Prow job artifacts/ci:analyze-prow-job-test-failureprowjob-url test-name [--fast]- Analyzes test errors from console logs and Prow CI job artifacts/ci:analyze-regression<regression id>- Analyze details about a Component Readiness regression and suggest next steps/ci:ask-sippy[question]- Ask the Sippy AI agent questions about OpenShift CI payloads, jobs, and test results/ci:check-if-jira-regression-is-ongoing<jira-key-or-url>- Check if the regression described in a Jira bug is still ongoing or has resolved/ci:extract-prow-job-must-gatherprowjob-url- Extract and decompress must-gather archives from Prow job artifacts/ci:fetch-payloads[architecture] [version] [stream]- Fetch recent release payloads from the OpenShift release controller/ci:fetch-test-report<test-name> [release]- Fetch a test report from Sippy showing pass rates, test ID, and Jira component/ci:list-step<workflow-or-chain-name>- List the step for the given workflow or chain name/ci:list-unstable-tests<version> <keywords> [sippy-url]- List unstable tests with pass rate below 95%/ci:payload-agent<payload-tag>- Autonomous agent that analyzes a rejected payload, determines root causes, and takes action based on confidence scoring/ci:query-job-status<execution-id>- Query the status of a gangway job execution by ID/ci:query-test-result<version> <keywords> [sippy-url]- Query test results from Sippy by version and test keywords/ci:revert-pr<pr-url> <jira-ticket>- Revert a merged PR that is breaking CI or nightly payloads/ci:trigger-periodic<job-name> [ENV_VAR=value ...]- Trigger a periodic gangway job with optional environment variable overrides/ci:trigger-postsubmit<job-name> <org> <repo> <base-ref> <base-sha> [ENV_VAR=value ...]- Trigger a postsubmit gangway job with repository refs/ci:trigger-presubmit<job-name> <org> <repo> <base-ref> <base-sha> <pr-number> <pr-sha> [ENV_VAR=value ...]- Trigger a presubmit gangway job (typically use GitHub Prow commands instead)
See plugins/ci/README.md for detailed documentation.
Automated code quality review with language-aware analysis for pre-commit verification
Commands:
/code-review:pr<pr-url-or-number> [--language <lang>] [--profile <name>] [--skip-build] [--skip-tests]- Automated PR code quality review with language-aware analysis and project-specific profiles/code-review:pre-commit-review[--language <lang>] [--profile <name>] [--skip-build] [--skip-tests]- Automated pre-commit code quality review with language-aware analysis and project-specific profiles
See plugins/code-review/README.md for detailed documentation.
Security compliance and vulnerability analysis tools for Go projects
Commands:
/compliance:analyze-cve<CVE-ID> [--algo=vta|rta|cha|static]- Analyze Go codebase for CVE vulnerabilities and suggest fixes
See plugins/compliance/README.md for detailed documentation.
Container image inspection and analysis using skopeo and podman
Commands:
/container-image:compare<image1> <image2>- Compare two container images to identify differences/container-image:inspect<image>- Inspect and provide detailed breakdown of a container image/container-image:tags<repository>- List and analyze available tags for a container image repository
See plugins/container-image/README.md for detailed documentation.
A plugin for engineering documentation and notes
Commands:
/doc:note[task description]- Generate professional engineering notes and append them to a log file
See plugins/doc/README.md for detailed documentation.
Etcd cluster health monitoring and performance analysis utilities
Commands:
/etcd:analyze-performance[--duration <minutes>]- Analyze etcd performance metrics, latency, and identify bottlenecks/etcd:health-check[--verbose]- Check etcd cluster health, member status, and identify issues
See plugins/etcd/README.md for detailed documentation.
Git workflow automation and utilities
Commands:
/git:backport<commit> <branch1> [branch2...] [--new-branch]- Backport commits to multiple branches/git:bisect[good-commit] [bad-commit]- Interactive git bisect assistant with pattern detection and automation/git:branch-cleanup[--dry-run] [--merged-only] [--remote]- Clean up old and defunct branches that are no longer needed/git:cherry-pick-by-patch<commit_hash>- Cherry-pick git commit into current branch by "patch" command/git:commit-suggest[N]- Generate Conventional Commits style commit messages or summarize existing commits/git:debt-scan- Analyze technical debt indicators in the repository/git:fix-cherrypick-robot-pr<pr-url> [error-messages]- Fix a cherrypick-robot PR that needs manual intervention/git:redescribe[pr-url]- Adapt and correct a PR description to match its code diffs and commit messages/git:suggest-reviewers[base-branch]- Suggest appropriate reviewers for a PR based on git blame and OWNERS files/git:summary- Show current branch, git status, and recent commits for quick context
See plugins/git/README.md for detailed documentation.
Run golang codebase related commands and tools
Commands:
/golang:lint-fix- Run golangci-lint tool and fix all reported issues
See plugins/golang/README.md for detailed documentation.
Gateway API management for Kubernetes/OpenShift clusters
Commands:
/gwapi:check[namespace]- Check Gateway API resources status in the cluster/gwapi:delete[namespace]- Delete Gateway API resources from a Kubernetes/OpenShift cluster/gwapi:install[namespace]- Install Gateway API resources to a Kubernetes/OpenShift cluster
See plugins/gwapi/README.md for detailed documentation.
Generate HyperShift cluster creation commands via hcp CLI from natural language descriptions
Commands:
/hcp:cluster-health-check<cluster-name> [--verbose] [--output-format json|text]- Perform comprehensive health check on HCP cluster and report issues/hcp:generate<provider> <cluster-description>- Generate ready-to-execute hypershift cluster creation commands from natural language descriptions
See plugins/hcp/README.md for detailed documentation.
A hello world plugin
Commands:
/hello-world:echo[name]- Hello world plugin implementation
See plugins/hello-world/README.md for detailed documentation.
A plugin to automate tasks with Jira
Commands:
/jira:backlog[project-key] [--assignee username] [--days-inactive N]- Find suitable JIRA tickets from the backlog to work on based on priority and activity/jira:categorize-activity-type<issue-key> [--auto-apply]- Categorize JIRA tickets into activity types using AI/jira:clone-from-github<issue-number> [issue-number...] [--github-project <org/repo>] [--jira-project <key>] [--dryrun]- Clone GitHub issues to Jira with proper formatting and linking/jira:create-release-note<issue-key>- Generate bug fix release notes from Jira tickets and linked GitHub PRs/jira:create<type> [project-key] <summary> [--component <name>] [--version <version>] [--parent <key>]- Create Jira issues (story, epic, feature, task, bug, feature-request) with proper formatting/jira:generate-feature-doc<feature-key>- Generate comprehensive feature documentation from Jira feature and all related issues and PRs/jira:generate-test-plan[JIRA issue key] [GitHub PR URLs]- Generate test steps for a JIRA issue/jira:grooming[project-filter] [time-period] [--component component-name] [--label label-name] [--type issue-type] [--status status] [--story-points]- Analyze new bugs and cards added over a time period and generate grooming meeting agenda/jira:issues-by-component<project-key> [time-period] [--component name] [--assignee username] [--reporter username] [--status status] [--search term] [--search-description]- List and analyze JIRA issues organized by component with flexible filtering/jira:reconcile-github[--github-project <org/repo>] [--jira-project <key>] [--profile <name>] [--porcelain] [--output json|yaml]- Reconcile state mismatches between GitHub and Jira issues/jira:setup-gh2jira- Install and configure the gh2jira utility with all required tools and credentials/jira:solve- Analyze a JIRA issue and create a pull request to solve it./jira:status-rollupissue-id [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]- Generate a status rollup comment for any JIRA issue based on all child issues and a given date range/jira:update-weekly-status[project-key] [--component name] [--label label-name] [user-filters...]- Update weekly status summaries for Jira issues with component and user filtering/jira:validate-blockers[target-version] [component-filter] [--bug issue-key]- Validate proposed release blockers using Red Hat OpenShift release blocker criteria
See plugins/jira/README.md for detailed documentation.
LVMS (Logical Volume Manager Storage) plugin for troubleshooting and debugging storage issues
Commands:
/lvms:analyze[must-gather-path|--live] [--component storage|operator|volumes]- Comprehensive LVMS troubleshooting - analyzes LVMCluster, volume groups, PVCs, and storage issues on live clusters or must-gather
See plugins/lvms/README.md for detailed documentation.
A plugin to analyze and report on must-gather data
Commands:
/must-gather:analyze[must-gather-path] [component]- Quick analysis of must-gather data - runs all analysis scripts and provides comprehensive cluster diagnostics/must-gather:ovn-dbs[must-gather-path]- Analyze OVN databases from a must-gather using ovsdb-tool/must-gather:windows[must-gather-path] [--component COMPONENT]- Analyze Windows node logs and issues in must-gather data
See plugins/must-gather/README.md for detailed documentation.
Kubernetes and OpenShift node health monitoring and diagnostics
Commands:
/node:cluster-node-health-check[--node <node-name>] [--verbose] [--output-format json|text]- Perform comprehensive health check on cluster nodes and report kubelet, CRI-O, and node-level issues
See plugins/node/README.md for detailed documentation.
Automatically create and apply tuned profile
Commands:
/node-tuning:analyze-node-tuning[--sosreport PATH] [--format json|markdown] [--max-irq-samples N]- Analyze kernel/sysctl tuning from a live node or sosreport snapshot and propose NTO recommendations/node-tuning:generate-tuned-profile[profile-name] [--summary ...] [--sysctl ...] [options]- Generate a Tuned (tuned.openshift.io/v1) profile manifest for the Node Tuning Operator
See plugins/node-tuning/README.md for detailed documentation.
OLM (Operator Lifecycle Manager) plugin for operator management and debugging
Commands:
/olm:approve<operator-name> [namespace] [--all]- Approve pending InstallPlans for operator installations and upgrades/olm:catalog<list|add|remove|refresh|status> [arguments]- Manage catalog sources for discovering and installing operators/olm:debug<issue-description> <must-gather-path> [olm-version]- Debug OLM issues using must-gather logs and source code analysis/olm:diagnose[operator-name] [namespace] [--fix] [--cluster]- Diagnose and optionally fix common OLM and operator issues/olm:install<operator-name> [namespace] [channel] [source] [--approval=Automatic|Manual]- Install a day-2 operator using Operator Lifecycle Manager/olm:list[namespace] [--all-namespaces]- List installed operators in the cluster/olm:opm<action> [arguments...]- Execute opm (Operator Package Manager) commands for building and managing operator catalogs/olm:search[query] [--catalog <catalog-name>]- Search for available operators in catalog sources/olm:status<operator-name> [namespace]- Get detailed status and health information for an operator/olm:uninstall<operator-name> [namespace] [--remove-crds] [--remove-namespace]- Uninstall a day-2 operator and optionally remove its resources/olm:upgrade<operator-name> [namespace] [--channel=<channel>] [--approve]- Update an operator to the latest version or switch channels
See plugins/olm/README.md for detailed documentation.
OLM team development utilities and onboarding tools
Commands:
/olm-team:configure-agent- Configure the k8s-ocp-olm-expert agent with local repository paths/olm-team:dev-setup[target-directory]- Set up OLM development repositories and onboard to the team/olm-team:ep-watch- Watch open Enhancement PRs from other teams that may impact OLM
See plugins/olm-team/README.md for detailed documentation.
OpenShift development utilities and helpers
Commands:
/openshift:add-enhancement[area] <name> <description> <jira>- Create a new OpenShift Enhancement Proposal/openshift:bootstrap-om- Bootstrap OpenShift Manager (OM) integration for OpenShift operators with automated resource discovery/openshift:bump-deps<dependency> [version] [--create-jira] [--create-pr]- Bump dependencies in OpenShift projects with automated analysis and PR creation/openshift:cluster-health-check[--verbose] [--output-format]- Perform comprehensive health check on OpenShift cluster and report issues/openshift:crd-review[repository-path]- Review Kubernetes CRDs against Kubernetes and OpenShift API conventions/openshift:create-cluster[release-image] [platform] [options]- Extract OpenShift installer from release image and create an OCP cluster/openshift:destroy-cluster[install-dir]- Destroy an OpenShift cluster created by create-cluster command/openshift:expand-test-case[test-idea-or-file-or-commands] [format]- Expand basic test ideas or existing oc commands into comprehensive test scenarios with edge cases in oc CLI or Ginkgo format/openshift:ironic-status- Check status of Ironic baremetal nodes in OpenShift cluster/openshift:new-e2e-test[test-specification]- Write and validate new OpenShift E2E tests using Ginkgo framework/openshift:node-kernel-conntrack<node> <image> [--command <cmd>] [--filter <params>]- Get connection tracking entries from Kubernetes node/openshift:node-kernel-ip<node> <image> --command <cmd> [--options <opts>] [--filter <params>]- Inspect routing, network devices, and interfaces on Kubernetes node/openshift:node-kernel-iptables<node> <image> --command <cmd> [--table <table>] [--filter <params>]- Inspect IPv4 and IPv6 packet filter rules on Kubernetes node/openshift:node-kernel-nft<node> <image> --command <cmd> [--family <family>]- Inspect nftables packet filtering and classification rules on Kubernetes node/openshift:rebase<tag>- Rebase OpenShift fork of an upstream repository to a new upstream release./openshift:review-test-cases[file-path-or-test-code-or-commands]- Review test cases for completeness, quality, and best practices - accepts file path or direct oc commands/test code/openshift:visualize-ovn-topology- Generate and visualize OVN-Kubernetes network topology diagram
See plugins/openshift/README.md for detailed documentation.
Helpers for openshift/origin development.
Commands:
/origin:two-node-origin-pr-helper[--url PR_URL] [<pr>] [--depth quick|full]- Expert review tool for PRs that add or modify Two Node (Fencing or Arbiter) tests under test/extended/two_node/ in openshift/origin.
See plugins/origin/README.md for detailed documentation.
Automate OpenShift Tests Extension (OTE) migration for component repositories
Commands:
/ote-migration:migrate- Automate OpenShift Tests Extension (OTE) migration for component repositories
See plugins/ote-migration/README.md for detailed documentation.
A plugin to save and resume conversation sessions across long time intervals
Commands:
/session:save-session[optional-description]- Save current conversation session to markdown file for future continuation
See plugins/session/README.md for detailed documentation.
Analyze sosreport archives for system diagnostics and troubleshooting
Commands:
/sosreport:analyze<path-to-sosreport> [--only <areas>] [--skip <areas>]- Analyze sosreport archive for system diagnostics and issues/sosreport:ovs-db[sosreport-path] [--db] [--flows-only] [--query <json>]- Analyze OVS data from sosreport (text files or database)
See plugins/sosreport/README.md for detailed documentation.
Team structure knowledge and health analysis commands for OpenShift teams
Commands:
/teams:health-check-jiras--project <project> [--component comp1 comp2 ...] [--team <team-name>] [--status status1 status2 ...] [--include-closed] [--limit N]- Query and summarize JIRA bugs for a specific project with counts by component/teams:health-check-regressions<release> [--components comp1 comp2 ...] [--team <team-name>] [--start YYYY-MM-DD] [--end YYYY-MM-DD]- Query and summarize regression data for OpenShift releases with counts and metrics/teams:health-check<release> [--components comp1 comp2 ...] [--team <team-name>] [--project JIRAPROJECT]- Analyze and grade component health based on regression and JIRA bug metrics/teams:list-components[--team <team-name>]- List all OCPBUGS components, optionally filtered by team/teams:list-jiras<project> [--component comp1 comp2 ...] [--status status1 status2 ...] [--include-closed] [--limit N]- Query and list raw JIRA bug data for a specific project/teams:list-regressions<release> [--components comp1 comp2 ...] [--start YYYY-MM-DD] [--end YYYY-MM-DD]- Fetch and list raw regression data for OpenShift releases/teams:list-teams- List all teams from the team component mapping
See plugins/teams/README.md for detailed documentation.
Analyze code coverage and identify untested paths
Commands:
/test-coverage:analyze<path-or-url> [--output <path>] [--priority <level>] [--test-structure-only]- Analyze test code structure without running tests to identify coverage gaps/test-coverage:gaps<test-file-or-url> [--output <path>]- Identify E2E test scenario gaps in OpenShift/Kubernetes tests (component-agnostic)
See plugins/test-coverage/README.md for detailed documentation.
Comprehensive testing utilities for operators and applications
Commands:
/testing:mutation-test[operator-path] [--controllers <controller1,controller2>] [--mutation-types <types>] [--report-format <format>]- Test operator controller quality through mutation testing - validates test suite catches code mutations
See plugins/testing/README.md for detailed documentation.
A generic utilities plugin serving as a catch-all for various helper commands and agents
Commands:
/utils:address-reviews[PR number (optional - uses current branch if omitted)]- Fetch and address all PR review comments/utils:auto-approve-konflux-prs<target-repository>- Automate approving Konflux bot PRs for the given repository by adding /lgtm and /approve/utils:generate-test-plan[GitHub PR URLs]- Generate test steps for one or more related PRs/utils:gh-attention[--repo <org/repo>]- List PRs and issues requiring your attention/utils:placeholder- Placeholder command for the utils plugin/utils:process-renovate-pr<PR_NUMBER|open> [JIRA_PROJECT] [COMPONENT]- Process Renovate dependency PR(s) to meet repository contribution standards/utils:review-ai-helpers-overlap[--idea TEXT] [--pr NUMBER] [--verbose]- Review potential overlaps with existing ai-helpers (Claude Code Plugins, Commands, Skills, Sub-agents, or Hooks) and open PRs/utils:review-security[file-paths-or-patterns]- Orchestrate security scanners and provide contextual triage of findings
See plugins/utils/README.md for detailed documentation.
Manage isolated git worktree workspaces for multi-repo development
Commands:
/workspaces:create<short-description> <repo1|url> [repo2...]- Create a workspace with git worktrees for multi-repository development/workspaces:delete<workspace-name>- Delete a workspace and its git worktrees
See plugins/workspaces/README.md for detailed documentation.
Generate comprehensive YAML documentation from Go struct definitions with sensible default values
Commands:
/yaml:docs[file:StructName] [output.md]- Generate comprehensive YAML documentation from Go struct definitions with sensible default values
See plugins/yaml/README.md for detailed documentation.