hyperfleet-claude-plugins

Manage Renovate/MintMaker dependency update PRs across HyperFleet repos — list, classify, approve, rebase, and merge

Validates JIRA tickets against HyperFleet ticket-hygiene standards — checks required fields, valid components, activity types, story points, and acceptance criteria. Suggests and applies fixes via jira CLI. Use when triaging tickets, validating sprint readiness, or asking "does this ticket have everything we need?"

Review a PR with JIRA validation, architecture checks, impact analysis, and interactive recommendations

Shows unassigned, non-blocked tickets in the current JIRA sprint backlog, sorted by priority, helping developers pick their next task.

Analyzes HyperFleet E2E CI pipeline failures from a Prow URL, GitHub Actions URL, job name, or JIRA ticket. Use when a nightly or periodic E2E pipeline run fails and you need a structured root cause analysis with confidence scoring.

Surface and prioritize open PRs across the openshift-hyperfleet org using GitHub + JIRA context, PR content analysis, and intelligent multi-factor scoring with confidence levels

Interactive assistant for authoring HyperFleet adapter configurations (AdapterConfig + AdapterTaskConfig YAML files)

Reviews all changes on the current branch against HyperFleet standards.

Audits local HyperFleet repositories for operational readiness using requirements fetched dynamically from the architecture repo via the hyperfleet-architecture skill. Checks health probes, dead man's switch metrics, retry logic, PDB, resource limits, graceful shutdown, and reliability documentation. READ-ONLY - does not modify any files.

TRIGGER: When the user asks to draft / generate / create release notes or a changelog for a HyperFleet release (e.g. "release notes for 0.3"). WHAT IT DOES: Produces a curated release-notes draft. A deterministic generator establishes the grounded ground truth (which tickets/CVEs shipped, categories, components, image digests); then this skill enriches it with JIRA ticket summaries, drafts the Overview and Highlights, trims insignificant entries, and renders the notes — every line traceable to a real ticket, nothing invented.

Analyzes code changes in HyperFleet component repositories (API, Sentinel, Adapter, Broker) to determine if architecture documentation needs updates using directory-based scope and complete document reading with single comprehensive LLM analysis. Activates when users ask "analyze architecture impact", "check if docs need update", or use /architecture-impact.

Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?"

Creates well-structured JIRA tickets in the HYPERFLEET project with required What/Why/Acceptance Criteria for all tickets, and required story points/activity type for Stories/Tasks/Bugs. Activates when users ask to create a ticket, story, task, or epic. Also activates when Claude itself decides a JIRA ticket should be created (e.g., follow-up from a PR comment, triaging work) — never use jira issue create directly, always use this skill.

Triage Jira bugs (New->Backlog) and GitHub issues for openshift-hyperfleet repos interactively.

Answers questions about HyperFleet architecture, design patterns, versioning strategies, cluster lifecycle, event-driven architecture, adapter framework, configuration standards, and git workflow by fetching docs from the openshift-hyperfleet/architecture GitHub repository.

Audits local HyperFleet repositories against team architecture standards dynamically fetched from the architecture repo. Activates when users ask to audit repos, check standards compliance, or identify standards gaps. Can also fix gaps when requested.

TRIGGER: When user asks to "implement", "automate", "generate", "update" test automation from a test case document or existing test code. WHAT IT DOES: Creates new or updates existing test automation by mapping test case steps to the HyperFleet E2E internal library architecture (pkg/) to ensure declarative, maintainable code.

Use when designing E2E test cases for HyperFleet epics or features - requires a Jira epic ticket ID to understand acceptance criteria, reads existing test cases from the repo, and produces structured test case documents following the project template

Checks whether a JIRA ticket's requirements and acceptance criteria are implemented in the current codebase. Use when the user asks if a ticket is implemented, wants to validate acceptance criteria against code, or asks "is this ticket done?"