stolostron

Monitor and analyze CVE (security) issues for Server Foundation team. Groups by CVE, creates one tracking task per CVE (consolidates all affected repositories), and performs deep impact analysis across all branches.

Fetch/Get/View all active(open) pull requests of sf(server foundation) team. For example: `How many sf PRs opened today?` sometimes user may omit `sf`, directly say `How many PRs opened today?`, if user's context does not contain any other PR related information, then it is assumed that the user intends to query the PRs of the sf team.

Analyze a Jira bug for Server Foundation relevance and reproducibility. Use this skill when the user wants to check if a bug can be reproduced, assess if it has enough information, or verify SF team ownership. Trigger phrases: 'analyze bug', 'check bug reproducibility', 'can we reproduce ACM-12345', 'is this bug reproducible', 'analyze ACM-12345', 'check if bug is SF-related'.

Orchestrate full bug reproduction workflow: analyze bug, provision ACM cluster, execute test, capture results, and post to Jira. Use this skill when the user wants to reproduce a bug end-to-end, set up a test environment for a bug, or says 'reproduce bug ACM-12345', 'test ACM-12345', 'reproduce this bug automatically'.

Generate an architectural overview of upstream OCM-io vs downstream stolostron repos for Server Foundation. Clones all repos, analyzes their code, and produces a Mermaid-diagrammed markdown file at the repo root. Trigger phrases: 'generate architecture doc', 'repo architecture', 'upstream downstream diagram', 'ocm vs stolostron', 'generate repo overview'.

Generate a bug triage report for the Server Foundation team. Use this skill when the user wants to triage bugs, review new issues, check for unassigned bugs, or says 'triage bugs', 'new bugs', 'bug review', 'unassigned bugs', 'vulnerability review'. Queries Jira for recently created or unresolved bugs and formats a triage summary.

Manage server foundation OCP cluster pools, cluster claims, and AWS resource cleanup. Use this skill when you need to claim/destroy clusters, check pool status, manage hibernation, track cluster ownership, or identify AWS resources for cleanup. For example: `Claim a cluster from sno-lite pool` or `Who owns cluster xyz?` or `Prevent my cluster from hibernating` or `What AWS resources need cleanup?`

Clone a repository and create a git worktree for a specific PR branch or a new development branch. MUST be used for ALL workspace operations — never use plain 'git clone' into workspace/. Use this skill when you need to check out PR code locally, or start new development on any SF repo. Trigger phrases: 'clone worktree', 'checkout PR', 'clone PR', 'worktree for PR', 'fix PR', 'new branch', 'start development'.

Use when the user wants GitHub PR diff analysis for any ACM-related repo to understand what changed (components, UI, filters, field order, controllers, CRDs, webhooks) and what to test -- WITHOUT running the full JIRA-to-Polarion test case generator pipeline. Defaults to stolostron/console and kubevirt-plugin when no repo is specified (backward compatible with acm-test-case-generator). TRIGGER: analyze PR #N, what changed in this merge, test impact of this diff. DO NOT TRIGGER: user wants Polarion test case from ACM-#### end-to-end (use acm-test-case-generator); user wants only domain facts (use acm-knowledge-base).

Use this skill when the user wants a FULL end-to-end Polarion-ready ACM Console UI test case from a JIRA ticket (e.g. ACM-30459): JIRA + PRs + UI discovery + synthesis + optional live validation + writing + mandatory quality review. This is the ONLY skill for that complete path. Do NOT use acm-test-case-writer or acm-qe-code-analyzer for the same request—they are partial workflows. Do NOT use acm-knowledge-base alone; it is reference-only. TRIGGER: generate/write test case from JIRA, Polarion test case for ACM ticket, test coverage for a story. DO NOT TRIGGER: PR-only diff analysis without JIRA-to-Polarion pipeline (use acm-qe-code-analyzer); review-only (use acm-test-case-reviewer).

Use when the user wants a QUALITY REVIEW of an existing ACM Console UI test case markdown file (conventions, discovered-vs-assumed UI, MCP spot-checks, AC consistency)— without re-running JIRA/PR/UI investigation. If the user just finished acm-test-case-generator, review is already Phase 7 inside that skill—do not invoke this unless reviewing a standalone file or an out-of-band draft. TRIGGER: review this test-case.md, pre-Polarion QA, validate test steps. DO NOT TRIGGER: full test case from JIRA (acm-test-case-generator).

Use ONLY when a Polarion-style ACM Console test case markdown must be authored from ALREADY-SYNTHESIZED investigation context (JIRA + code + UI summary present in the thread or artifacts)—not for starting from a bare JIRA ID. For starting from JIRA, use acm-test-case-generator instead. TRIGGER: user explicitly asks to convert existing synthesis into test-case.md; Phase-6-style write with context already in hand. DO NOT TRIGGER: user gives only ACM-#### and expects full pipeline; user wants PR diff analysis only (acm-qe-code-analyzer); user wants quality review only (acm-test-case-reviewer).

Executes an existing ACM Console UI test case step-by-step against a live environment and produces a per-step pass/fail report with evidence (screenshots, CLI output, accessibility snapshots). Takes a test case markdown file, Polarion ID, or inline content as input. Does NOT generate or modify test cases -- only validates them. TRIGGER: validate test case, execute test case, run test case on cluster, validate RHACM4K-XXXXX on environment, dry-run test case, check if test case passes. DO NOT TRIGGER: generate test case from JIRA (use acm-test-case-generator); review test case quality/format (use acm-test-case-reviewer); verify a bug fix (use acm-bug-fix-verifier).

Enrich test failure data with AI-analyzed context -- resolve page objects, verify selector existence in product source, analyze selector change history, and fill feature knowledge gaps. Use when test failure data needs enrichment before classification analysis.

Analyze Jenkins pipeline test failures and classify each as PRODUCT_BUG, AUTOMATION_BUG, INFRASTRUCTURE, or NO_BUG. Runs a 4-stage pipeline with data gathering, cluster diagnostics, AI classification, and report generation. Use when asked to analyze a Jenkins run, classify test failures, or investigate pipeline results.

Verifies whether a known ACM bug fix has landed on a target environment. Takes a JIRA ticket and a cluster, runs a 7-phase pipeline: parallel JIRA/PR/environment investigation, three-tier fix presence check (branch reachability, build date, code presence), PR code review for fix correctness, Neo4j prerequisite gap analysis with heuristic fallback, Playwright-driven UI/API verification, and verdict with optional JIRA update. Produces BLOCKED, NOT_FIXED, PRESENT, or VERIFIED verdicts with evidence trail. TRIGGER: verify bug fix, confirm fix landed, check if fixed, is the bug fixed, verify ACM-NNNNN on cluster, test fix on environment. DO NOT TRIGGER: hunt for new bugs (use acm-bug-hunter), write test cases (use acm-test-case-generator), cluster health check (use acm-hub-health-check), PR-only code review (use acm-qe-code-analyzer).

Add FBC support for new OCP version in Konflux release data - creates overlays, tenant config, and RPA entries.

Get FBC catalog URLs for QE sharing (Release CRs, snapshots, or prod index)

Update Konflux Dockerfile version labels across Submariner repositories

Update bundle component image SHAs from Konflux snapshots - automates SHA extraction, config file updates, bundle regeneration, and verification

Automate Konflux bundle setup on new release branches - configures Tekton pipelines for bundle builds including infrastructure, OLM annotations, hermetic builds, and multi-platform support

Automate Konflux component setup on new release branches - configures Tekton pipelines, Dockerfiles, RPM lockfiles, and hermetic builds for Submariner components. Supports 8 component types. Arguments are optional and order-independent.

Configure Konflux for new Submariner version - creates overlays, tenant config, and RPAs for Y-stream releases.

Add release notes from Jira, then per-issue agent review

Agent workflow defaults for GitHub PR work and GitLab GH release pipeline handoffs — DCO sign-off, PR comments after push, merge pipeline fixes to the run branch (main) before telling the user to rerun. Use when creating or updating PRs, fixing acm-global-hub-release GitLab jobs, pushing fixes, babysitting CI, retesting, or when the user asks about agent config or PR conventions.

Two-phase workflow for processing Jira CVE tickets across any project. Driven by a configurable JSON mapping file (component → repo → branch → local path). Phase 1: analyze each ticket and write cve_summaries/<release>/*.md resolution files plus a combined _phase1_summary.md. Phase 2: after user review, create or update PRs (new, grouped, or stacked on existing). Detects open PRs touching the same go.mod to avoid merge conflicts. Use when the user says "fix this CVE", "process these CVE tickets", "analyze CVE issues", or provides a Jira CSV export or list of ACM/OADP/other Jira keys with CVE titles.

Global Hub GitLab release pipeline (vbirsan/acm-global-hub-release). Use when fixing validate-release or trigger-jenkins scripts, telling the user to rerun a pipeline, debugging failed GitLab jobs, or changing Jira param parsing in chunlin-acm-global-hub-release. Enforces push script fixes to GitLab and merge-to-run-branch before handoff.

Run Global Hub Jenkins e2e pipeline manually and upload results to Polarion. Use when resuming a failed globalhub-main pipeline, triggering regionalhub-import, triggering globalhub-e2e, or uploading e2e results to Polarion.

Create or update ACM Jira issues via API with required hygiene fields (Component Global Hub, Assignee, Activity Type, Severity, Priority). Use when creating sub-tasks, QE tasks, linking issues, or when the user asks about Jira API tokens, ACM issue fields, or release-management component alerts.

Automated AMQ Streams and Kafka version update workflow for Multicluster Global Hub. Checks current versions, discovers latest available from RedHat operators catalog (stable channel), creates PR with updates, monitors CI checks, and transitions Jira task to Review state. Use when upgrading AMQ Streams operator or Kafka versions in Global Hub.

Analyze the Jenkins URL # and fix the automation issues:

Generate automation scripts based on Plarion ID #:

Smart Test Selection - Analyze GitHub PR and Select Relevant Tests

Assess the risk of changing hub cluster kube-apiserver certificates on clusters with ACM. Evaluates impact of certificate type changes, rotations, root CA changes, and intermediate CA changes. Provides risk analysis and mitigation guidance. Accepts --kubeconfig (optional, defaults to KUBECONFIG env var) and --new-cert (required) parameters.

Checks hub cluster kube-apiserver certificate configuration and its compatibility with ACM. Detects certificate type, validates configuration, and provides recommendations for both pre-installation and post-installation scenarios.

Automate complete Multicluster Global Hub release workflow across 6 repositories including branch creation, OpenShift CI configuration, catalog OCP version management, bundle updates, and PR creation. REQUIRES explicit RELEASE_BRANCH specification (e.g., RELEASE_BRANCH=release-2.17). Supports two modes - CREATE_BRANCHES=true (create branches) or false (update via PR). Keywords: release branch, global hub, openshift/release, catalog, bundle, CI configuration, OCP versions.

Verify a Jira bug fix on the user's daily development cluster. Fetches issue details, runs cluster-side checks, simulates the failure scenario if needed, confirms the fix works, and posts findings back to Jira. Use when asked to "verify [JIRA-ID] on the cluster", "test the fix", or "check the cluster state for [issue]".

Use when installing, configuring, or redeploying OpenShell for the Swarmer project — covers both local kind clusters and OpenShift clusters, SCC fixes, cert extraction and validation, secret creation, and wiring the deployment manifest.

Works on the stolostron/mtv-integrations Go repo: ACM MTV provider controller, Plan validating webhook (UserPermission + impersonation), Helm charts under charts/ (keep in sync with config/), and addons. Use when editing this repository, MTV/ACM integration, ManagedCluster providers, forklift Plans, validating webhook RBAC, Helm chart templates, golangci-lint, gofmt, or Go style fixes.