This repository also configures its own agents. See what ai-helpers tells them →
Skill Claude Code needs its repo
Orchestrates the Quay bug-fix workflow through 9 phases with confidence-based gating. Reads confidence from phase artifacts to advance automatically, post JIRA comments, or escalate to the user.
Skill Claude Code
Root cause analysis for a Quay bug. Traces code paths through Quay subsystems, analyzes git history, forms and tests hypotheses, and enumerates complete state space.
Skill Claude Code needs its repo
Create comprehensive documentation for a Quay bug fix: JIRA ticket update, release notes, changelog entry, PR description, and team communication.
Skill Claude Code
Systematically reproduce a Quay bug using project-specific tooling. Documents environment, reproduction steps, and observable behavior.
Skill Claude Code
Critically evaluate a bug fix and its tests. Forms a verdict (inadequate / tests incomplete / solid) and recommends next steps.
Skill Claude Code
Scan all workflow artifacts and present a synthesized summary of findings, decisions, and status. Can be invoked at any point mid-workflow.
Skill Claude Code needs its repo
Query PROJQUAY Jira for open CVE tickets. Extracts CVE IDs, container names, packages, and target branches. Saves results to artifacts.
Skill Claude Code
Quay-specific Go stdlib CVE fix via quay-konflux-components. Bumps go-toolset image tag in the component Containerfile.
Skill Claude Code needs its repo
Quay CVE fix orchestrator. Enforces branch cascade and EOL rules, manages git worktrees, delegates language fixes to /cve:fix- plugin skills, and Konflux stdlib fixes to fix-konflux-stdlib. PR creation via /dev:pr.
Skill Claude Code needs its repo
State-machine workflow for Quay RC deployment on ephemeral OpenShift clusters. Provisions cluster, configures Konflux image mirroring, installs storage, deploys quay-operator from FBC catalog, validates the UI with Playwright, and optionally black-box tests a specific feature.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: