konflux-ci

Use when needing to understand Konflux architecture, design decisions, service responsibilities, APIs, build/test/release workflows, or how Konflux components fit together.

Use when needing to know which Red Hat team owns a Konflux-related repository (konflux-ci, hermetoproject, conforma orgs), which JIRA project or component to file issues against, or how the Red Hat Konflux engineering organization maps to the codebase.

Use when updating a Maven project to source its dependencies from a trusted Maven repository instead of Maven Central.

Use to trigger component builds, releases or get a component or application status

Use when tracing Konflux builds from image references, finding build logs from artifacts, or verifying source commits for container images - extracts provenance attestations to navigate from images back to builds and source code

Use when GitHub PR or branch has failing checks and you need to find Konflux pipeline information (cluster, namespace, PipelineRun name). Teaches gh CLI commands to identify Konflux checks (filter out Prow/SonarCloud), extract PipelineRun URLs from builds and integration tests, and parse URLs for kubectl debugging.

Use when Konflux pipelines fail, are stuck, timeout, or show errors like ImagePullBackOff. Covers PipelineRun failures, TaskRun issues (Pending, Failed, stuck Running), build errors, and systematic debugging of Tekton pipeline problems using kubectl and logs.

Use when user asks to "test skill invocation framework" or mentions "canary skill test". This is a self-test skill to verify the test framework correctly loads and invokes skills.

Debug failed Konflux e2e test runs by downloading logs and artifacts from GitHub Actions or OpenShift CI (Prow), analyzing test failures, and suggesting fixes. Use when the user asks to debug, investigate, or fix a failing e2e test, CI failure, or flaky test.

Use when reviewing, triaging, or retro-analyzing MintMaker/Renovate dependency PRs and their manifest companion PRs in konflux-ci/konflux-ci. Covers which PRs to skip, which to review lightly, label timing, and expected lifecycle.

Use when konflux-ci/konflux-ci PRs touch go.mod, go.sum, the go directive, golangci-lint or controller-gen pins, or deploy/e2e scripts that run go or make; or when CI logs show go.mod requires go >=, GOTOOLCHAIN/local mismatch, or OpenShift Prow failures on deploy-konflux-on-ocp.sh (cd operator; make install) or controller-gen.

Update upstream Konflux component versions. Use when bumping component versions, updating refs, or syncing to latest upstream.

Use when iteratively verifying operator changes in development — code edit, stop operator, optionally regenerate manifests or CRDs, restart operator, verify. Use when the user says "verify", "test this change", "restart the operator", or needs a stop-rebuild-run cycle.

Ginkgo/Gomega testing patterns for Konflux — test cleanup (envtest), Eventually/Consistently soft assertions, and helper conventions. Use when writing or reviewing Ginkgo tests.

Deploy Konflux on a local Kind cluster. Supports development mode (operator outside cluster for fast iteration) and preview mode (operator deployed in-cluster from release/build). Use when the user wants to start, restart, or recreate a local Konflux environment, run the operator locally, install integrations like sigstore or quay, or troubleshoot local deployment.

Create pull requests for konflux-ci repository. Explains CI behavior differences between fork and same-repo PRs, and the /allow command. Use when creating a PR, CI not running, or asking about fork PRs.

Onboard repositories to Codecov for unit test coverage tracking. Use this skill when users want to add Codecov integration, configure coverage uploads with flags, or set up CI pipelines to report coverage. Works with GitHub Actions, OpenShift CI (Prow), and GitLab CI. Supports public Codecov (app.codecov.io) and self-hosted Codecov instances.

Use when bulk-onboarding multiple repos to Codecov from an audit CSV, or when user says "bulk codecov", "prepare codecov", "enable codecov", "codecov from audit", "onboard repos to codecov", "apply codecov changes", "open the MRs", "push those changes", "enable coverage for all repos", "prepare local for audit.csv". Not for single-repo interactive onboarding (codecov-onboarding) or E2E instrumentation (coverport-integration).

Audit a GitHub/GitLab organization's repositories for code coverage status. Generates CSV spreadsheet showing which repos have tests, Codecov integration, and what's missing. Use when user asks to audit an org, create a coverage spreadsheet, or assess coverage gaps across repositories. Also works with pre-existing repo lists (JSON, CSV, text files) spanning multiple orgs/groups.

Checklist for merge-ready PRs in coverport. Use when preparing a PR for review or verifying a PR meets all requirements before merging.

Use when asked to add, create, or generate a .codecov.yml file for a repository and open a PR or MR. Supports GitHub and GitLab repositories. Triggers on requests like "add codecov config", "create codecov yml", "set up codecov for repo X", "add coverage config to repo".

Generate and create Jira tasks for code coverage onboarding from an audit CSV. Two-phase workflow — dry-run generates task files locally for review, then create-tasks pushes them to Jira under a target epic. Use when user wants to create Jira tasks from an audit spreadsheet, convert coverage audit results into actionable work items, or batch-create Jira issues for coverage gaps across an org. Also use when user mentions "jira tasks from audit", "coverage onboarding tasks", "create tasks for repos without coverage", or wants to track coverage work in Jira.

Integrate coverport into repositories to enable e2e test coverage collection and upload to Codecov. Supports Go, Python, and Node.js applications with Tekton/Konflux pipelines and GitHub Actions (using coverport CLI container via podman). Use this skill when users ask to integrate coverport, add e2e coverage tracking, or set up coverage instrumentation.

Generate code coverage for C/C++ projects using gcov and lcov, and upload to Codecov. Use this skill when users need to add coverage to C or C++ projects, set up lcov pipelines, or troubleshoot gcov/lcov issues. Covers autotools, CMake, and Meson build systems.

Use when CI checks fail unexpectedly, when preparing code for CI, or when encountering non-obvious build and pipeline behavior. Covers vendoring, hermetic builds, security scans, code generation checks, coverage, and webhook validation gotchas.

Use when debugging integration-service running on a cluster. Covers pod logs, health probes, metrics, webhooks, network policies, environment variables, snapshot GC, and common failure modes.

Use when setting up a local development environment, deploying integration-service to a cluster, installing CRDs, or tearing down a Kind cluster. Covers make targets, kustomize deployment, and full Konflux stack setup.

Use when preparing a pull request for review, before pushing, or when reviewing someone else's PR. Checklist of CI checks, commit conventions, code generation, testing, and documentation requirements.

Use when building, configuring, or running e2e tests for integration-service against a real cluster (Kind or OpenShift). Covers environment variables, test framework, Ginkgo flags, CI pipeline, and test repos.

Use when running, writing, or troubleshooting unit tests for integration-service. Covers make test, envtest setup, suite patterns, mock loader, CRD discovery, coverage, and common test failures.

Use when adding new tools, binaries, or packages to the konflux-test container image. Covers artifacts.lock.yaml (generic binaries), rpms.in.yaml (system packages), multi-architecture support, and hermetic build constraints.

Use when CI checks fail unexpectedly, when preparing code for CI, or when encountering non-obvious build and pipeline behavior. Covers hermetic builds, Tekton pipelines, multi-arch, GitHub Actions checks, and integration test structure.

Use when preparing a pull request for review or before pushing. Checklist of commit conventions, Rego policy tests at 100% coverage, BATS tests, code quality checks, and CI check requirements.

Use when running OPA policy unit tests, BATS bash tests, shellcheck, hadolint, or conftest integration tests locally. Covers test commands, coverage requirements, test data, and prerequisites.

Use when adding or modifying bash utility functions in test/utils.sh. Covers naming conventions, function structure, BATS tests, mock patterns for external tools, TEST_OUTPUT format, and shellcheck compliance.

Use when writing, modifying, or reviewing OPA/conftest Rego policies. Covers package naming, rule prefixes (violation_ and warn_), conftest namespaces, violation object structures, imports, and unit test patterns.

Gotchas when updating Go dependencies

Gotchas when editing Helm chart templates

Gotchas when debugging a deployed Squid instance

Gotchas when setting up or tearing down the local kind cluster

Gotchas when running unit or E2E tests

Gotchas when modifying CI/Tekton pipelines

Use when CI behaves unexpectedly, when you need to understand how Tekton bundles are built, or when understanding non-obvious behavior with templated workflows, Checkton, migration validation, kustomize checks, or trusted artifacts generation.

Use when a scan task fails in a pipeline, when task results have unexpected values, when understanding scan output formats, or when debugging bundle build failures.

Use before pushing a PR for review, when CI checks fail, or when reviewing someone else's PR. Pre-push checklist covering all CI requirements, commit conventions, and documentation for task catalog PRs.

Use when creating task variants (remote, trusted-artifacts), working with recipe.yaml files, or when the check-ta CI workflow fails. Covers both Go generators, the recipe format, and the generation pipeline.

Use when creating a new task version, bumping version labels, writing migration scripts, or when versioning/migration CI checks fail. Covers version labels, CHANGELOG.md, migration scripts with pmt modify, and kustomized variant updates.

Use when writing tests for a Tekton task, running tests locally, debugging test failures in CI, or understanding the three testing layers (Kind cluster, Tekton integration, ShellSpec).

Use when confused by CI behavior, investigating why tests did or did not run, or troubleshooting GitHub Actions workflows

Use when a Tekton task test fails in CI or locally and you need to find the root cause

Use when preparing, reviewing, or finalizing a pull request to this Tekton catalog repository

Use when running, writing, or troubleshooting functional tests for Tekton tasks in this catalog

Use when setting up or tearing down a local kind cluster for running Tekton task tests

Capture UI screenshots of changed components for PRs or testing. Take screenshots, screenshot UI changes, capture UI, visual diff, screenshot pull request changes, PR screenshots

Create a pull request, open a PR, submit a PR, push and create PR, send for review, open pull request, make a PR, raise a pull request

Debug e2e test failures, triage CI failures, analyze Cypress test logs, investigate flaky tests, diagnose test failures, check PR test results, why did tests fail, debug cypress, analyze test artifacts

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Create a Jira ticket, file a bug, open a Jira issue, draft a story, log a spike, raise an issue, create a task, report a bug, write a ticket, submit a Jira, new Jira ticket, open a task, file an issue, draft a bug report, create Jira bug, create Jira task

Use when checking formatting, linting, type errors, or security issues in the mobster repository — ruff, pylint, mypy, bandit, yamllint, pip-audit

Use when preparing a new release of mobster — release-please, version bump, GitHub release, PyPI, container image

Use when running integration tests in the mobster repository — requires docker compose, tests OCI registry interactions, cosign, syft, and TPA upload flows

Use when running, filtering, debugging, or adding unit tests in the mobster repository — tox, pytest, coverage

Use when writing, updating, or adding documentation for mobster commands, features, or developer internals — covers file placement and mkdocs.yml nav rules

Use when the user confirms paste-ready PR materials, or asks for a PR title/body, commit message, or CHANGELOG entry after substantive pulp-tool repo changes.

Use when changing the Dockerfile, .tekton/ PipelineRuns, pulp-tool-container image, UBI/Python base, or Konflux container build integration. Container images are built by Konflux Tekton — not GitHub Actions.

Use when changing upload, global CLI flags (--config, --build-id, --namespace), --rpm-path, --parent-package, --sbom-path, --artifact-results, Tekton workspace paths, or Konflux downstream integration. Container image *build*: changing-pulp-container.

Use when make test-diff-coverage fails, CI reports diff coverage below 100%, or a GitHub PR is blocked on uncovered changed lines.

Use when pre-commit hooks fail repeatedly, lint errors persist after make format, or local checks disagree with CI on pulp-tool.

Step-by-step guide for adding a new Tekton Task or updating an existing one in tekton-tools. Use when the user wants to create a task, bump a version, write a migration, or needs to know the required file structure.

Non-obvious CI/CD details, environment quirks, and gotchas specific to tekton-tools. Use when the user is confused by CI behavior, asks about Konflux pipelines, Renovate, or needs to understand how the CI environment differs from expectations.

Troubleshoot failing Konflux CI pipelines in tekton-tools. Use when a PR check fails, the user needs to find logs, interpret task results, or diagnose why a specific pipeline stage errored.

Checklist of requirements for a merge-ready pull request in tekton-tools. Use when the user asks what is needed to merge a PR, wants a review checklist, or is preparing changes for submission.

Run linters and validation checks for tekton-tools. Use when the user asks to run tests, validate changes, check YAML, lint commits, or wants to know what CI checks before merging.