Openshift Hyperfleet Hyperfleet Claude Plugins
openshift-hyperfleet-hyperfleet-claude-plugins is a Claude Code plugin marketplace for the Build phase that delivers five HyperFleet team standards, Jira workflows, and devtools plugins.
by openshift-hyperfleet · github.com/openshift-hyperfleet/hyperfleet-claude-plugins
Add HyperFleet’s five-plugin Claude Code marketplace for team standards, Jira-ready workflows, architecture guidance, and operational hygiene on OpenShift-style fleets.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install openshift-hyperfleet-hyperfleet-claude-plugins@openshift-hyperfleet/hyperfleet-claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:openshift-hyperfleet/hyperfleet-claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:openshift-hyperfleet/hyperfleet-claude-plugins").
What it does
openshift-hyperfleet-hyperfleet-claude-plugins is a Claude Code plugin marketplace maintained for HyperFleet development, packaging team standards, workflows, and platform-minded best practices into five installable plugins. It helps builders and platform engineers keep architecture decisions, Jira traceability, sprint hygiene, and operational readiness consistent when working on OpenShift-adjacent fleets. Solo builders wearing a platform hat can still use it to force structured specs, ticket updates, and reliability checks before merge or deploy. The set is opinionated and organization-flavored, so value peaks when your process already resembles enterprise fleet delivery. Treat it as a workflow accelerator that sits between planning artifacts and implementation, not as a replacement for your cluster tooling or official Red Hat support channels.
Highlights
- Five-plugin marketplace for HyperFleet development standards and best practices
- Jira CLI integration for tickets, sprints, story readiness, and impact estimation
- Architecture, reliability, and operational hygiene patterns for fleet-style deployments
- Developer documentation, versioning, and devtools assistance plugins
- Team workflow plugins rather than a single-purpose API connector
Why builders use it
Platform teams scatter standards, Jira steps, and readiness checks across wikis while the agent improvises without fleet-specific guardrails.
After registering the marketplace, Claude Code follows HyperFleet-oriented specs, Jira flows, and hygiene plugins so delivery stays consistent with team practice.
At a glance
- Type - Plugin in DevOps.
- Adoption - 0 installs, 5 stars, 0 votes.
FAQ
Who is openshift-hyperfleet-hyperfleet-claude-plugins for?
It is for HyperFleet and OpenShift-hyperfleet contributors who want Claude Code plugins for standards, Jira, and operational workflows.
When should I use openshift-hyperfleet-hyperfleet-claude-plugins?
Use it when you are writing specs, sizing stories, or implementing services that must match HyperFleet team practices and ticket hygiene.
How do I add openshift-hyperfleet-hyperfleet-claude-plugins to my agent?
Register the openshift-hyperfleet/hyperfleet-claude-plugins repository as a Claude Code marketplace, then enable the five plugins that match your role and connect Jira credentials if you use Jira CLI features.
Comments
Share how you use openshift-hyperfleet-hyperfleet-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.