Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Statically analyze Go test files—including unit, integration, and Ginkgo E2E tests for Kubernetes/OpenShift—to identify untested functions, paths, and scenarios without running tests. Generate HTML, JSON, or text reports detailing coverage gaps and test structure.
npx claudepluginhub openshift-eng/ai-helpers --plugin test-coverageShare bugs, ideas, or general feedback.
A collection of Claude Code plugins to automate and assist with various development tasks.
Add the marketplace:
/plugin marketplace add openshift-eng/ai-helpers
Install a plugin:
/plugin install jira@ai-helpers
Use the commands:
/jira:solve OCPBUGS-12345 origin
To get the latest plugin versions:
Update the marketplace (fetches latest plugin catalog):
/plugin marketplace update ai-helpers
Reinstall the plugin (downloads new version):
/plugin install <plugin>@ai-helpers
Add a SessionStart hook to automatically sync the marketplace catalog on each session. In your project's .claude/settings.json:
{
"hooks": {
"SessionStart": [
{
"command": "claude plugin marketplace update ai-helpers",
"timeout": 30000
}
]
}
}
Note: This only refreshes the catalog (what's available). To actually update an installed plugin to a newer version, you still need to reinstall it with /plugin install <plugin>@ai-helpers.
Cursor is able to find the various commands defined in this repo by
making it available inside your ~/.cursor/commands directory.
$ mkdir -p ~/.cursor/commands
$ git clone git@github.com:openshift-eng/ai-helpers.git
$ ln -s ai-helpers ~/.cursor/commands/ai-helpers
A container is available with Claude Code and all plugins pre-installed.
podman build -f images/Dockerfile -t ai-helpers .
To use Claude Code with Google Cloud's Vertex AI, you need to pass through your gcloud credentials and set the required environment variables:
podman run -it \
-e CLAUDE_CODE_USE_VERTEX=1 \
-e CLOUD_ML_REGION=your-ml-region \
-e ANTHROPIC_VERTEX_PROJECT_ID=your-project-id \
-v ~/.config/gcloud:/home/claude/.config/gcloud:ro \
-v $(pwd):/workspace \
-w /workspace \
ai-helpers
Environment Variables:
CLAUDE_CODE_USE_VERTEX=1 - Enable Vertex AI integrationCLOUD_ML_REGION - Your GCP region (e.g., us-east5)ANTHROPIC_VERTEX_PROJECT_ID - Your GCP project IDVolume Mounts:
-v ~/.config/gcloud:/home/claude/.config/gcloud:ro - Passes through your gcloud authentication (read-only)-v $(pwd):/workspace - Mounts your current directory into the containerYou can execute Claude Code commands directly without entering an interactive session using the -p or --print flag:
podman run -it \
-e CLAUDE_CODE_USE_VERTEX=1 \
-e CLOUD_ML_REGION=your-ml-region \
-e ANTHROPIC_VERTEX_PROJECT_ID=your-project-id \
-v ~/.config/gcloud:/home/claude/.config/gcloud:ro \
-v $(pwd):/workspace \
-w /workspace \
ai-helpers \
--print "/hello-world:echo Hello from Claude Code!"
This will:
/hello-world:echo command with the provided messageFor a complete list of all available plugins and commands, see PLUGINS.md.
Want to contribute or create your own plugins? Check out the plugins/ directory for examples.
Make sure your commands and agents follow the conventions for the Sections structure presented in the hello-world reference implementation plugin (see hello-world:echo for an example).
Plugins, commands, skills, and hooks must NEVER reference real people by name, even as stylistic examples (e.g., "in the style of ").
Ethical rationale:
Instead, describe specific qualities explicitly
Good examples:
When you identify a desirable characteristic (clarity, brevity, formality, humor, etc.), describe it explicitly rather than using a person as proxy.
Check for overlaps first - Before coding, validate your idea:
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimAnalyze code coverage metrics, identify untested code, and generate comprehensive coverage reports
Comprehensive testing utilities for operators and applications
Commands for code review, testing, and analysis
Use this agent for analyzing test results, synthesizing test data, identifying trends, and generating quality metrics reports. This agent specializes in turning raw test data into actionable insights that drive quality improvements. Examples:\n\n<example>\nContext: Analyzing test suite results
Analyze sosreport archives for system diagnostics and troubleshooting
LVMS (Logical Volume Manager Storage) plugin for troubleshooting and debugging storage issues
Container image inspection and analysis using skopeo and podman
Security compliance and vulnerability analysis tools for Go projects
Etcd cluster health monitoring and performance analysis utilities
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability. Use when reviewing tests or improving test quality.
Agentic Quality Engineering — AI-powered QE platform with 60 specialized agents, 75+ skills, sublinear coverage analysis, ReasoningBank pattern learning, and deep MCP integration for Claude Code and 11 coding agent platforms