add-or-update-taskStep-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.ci-cd-quirksNon-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.debug-ci-failuresTroubleshoot 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.pr-definition-of-doneChecklist 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-lints-and-testsRun 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.
リポジトリエクスプローラー
konflux-ci · リポジトリと代表的な skills - 2ページ
43 件の GitHub リポジトリにある 139 件の収集済み skills をリポジトリ単位で表示します。
adding-a-subcommandUse when adding a new CLI subcommand to qe-tools, or when understanding the pattern existing commands followci-cd-quirksUse when confused by CI behavior, investigating why a workflow failed, or troubleshooting environment variable issues in qe-toolsdebugging-cli-locallyUse when debugging qe-tools commands locally, investigating panics or unexpected output, or setting up a local development environmentpr-definition-of-doneUse when preparing, reviewing, or finalizing a pull request to the qe-tools repositoryrunning-testsUse when running, writing, or troubleshooting unit tests for qe-tools commands or packages
pr-definition-of-doneUse before opening or updating a konflux-clamav pull request, or when GitHub Actions or Konflux pipeline checks fail. Covers commits, formatting, lockfiles, and expected CI outcomes.ci-pipeline-debuggingUse when a Konflux Tekton build fails for konflux-clamav, when tracing task order or OCI artifacts, or when post-build security scans or the clamav-self-test integration pipeline fail.daily-db-updateUse when ClamAV signatures in the published image are stale, when fetch-db-data or freshclam fails on push builds, or when verifying that main-branch builds still run on schedule.hermetic-build-depsUse when changing RPMs, lockfiles, prefetch artifacts, or multi-arch inputs for the konflux-clamav hermetic image build. Covers rpms.in.yaml, rpm-lockfile-prototype, Hermeto prefetch, fetch-db-and-tools.sh, and Dockerfile COPY paths.
ci-pipeline-debuggingUse when a Tekton build pipeline fails, when you need to understand task ordering or resource requirements, or when debugging security scan failures. Covers PR and push pipeline differences, the fetch-db-data step, and all security scan tasks.daily-db-updateUse when troubleshooting the automated daily vulnerability database update, understanding the build trigger flow, or debugging fetch-db-data failures. Covers the GitHub Actions cron, push pipeline, matcher.db lifecycle, and manual triggering.hermetic-build-depsUse when adding, updating, or troubleshooting RPM or artifact dependencies for the hermetic build. Covers rpms.in.yaml, rpms.lock.yaml, artifacts.lock.yaml, epel.repo, Cachi2 prefetching, and the Dockerfile install step.pr-definition-of-doneUse when preparing a pull request for review or when CI checks fail. Checklist covering commit conventions, Dockerfile linting, formatting rules, security, and all CI checks that run on PRs.
ci-quirksDocuments merge-blocking CI pipelines and non-obvious constraints (AGENTS.md line limit, serial tests, multi-arch builds). Use when CI fails unexpectedly, adding CI-visible files or env vars, or checking what blocks merge.add-probe-scriptUse when adding, modifying, or removing an embedded probe script in cmd/scripts/, or when a liveness/readiness probe needs a new health check shell scriptdebug-instanceUse when a running smee-sidecar pod is unhealthy, restarting, not relaying events, or showing unexpected metricskind-clusterUse when setting up, running, or tearing down a Kind cluster for smee-sidecar system tests, or when system tests fail in CI
devlakeThis skill should be used whenever the user asks about engineering metrics, software delivery performance, or team productivity data — including PR statistics, DORA metrics (deployment frequency, lead time, change failure rate, recovery time), code coverage,…reportTrigger when the user wants a formatted HTML report file — DORA metrics report, PR cycle time report, engineering excellence report, coverage report, or retest analysis report. Not for quick questions (use devlake skill instead).scaffold-report-repoTrigger when the user wants to create a new GitLab repo for automated, scheduled engineering reports — setting up CI pipelines, DSPy prompts, and GitLab Pages publishing from DevLake data.
building-and-lintingUse when building the binary or container image, running linters, or troubleshooting build failures. Covers Makefile targets, golangci-lint setup, Dockerfile structure, and YAML linting.ci-cd-quirksUse when CI checks fail unexpectedly, when modifying Tekton pipelines or GitHub Actions, or when debugging build or test failures in CI. Covers pipeline structure, GitHub Actions workflows, Renovate config, and hermetic builds.running-testsUse when running, writing, or troubleshooting unit tests or e2e tests for etcd-shield. Covers make test, Ginkgo patterns, Chainsaw acceptance tests, coverage collection, and common test failures.
lint-and-testRun the project's tox linting and test suite and present a concise pass/fail summary. Use when asked to lint, test, check, or validate the project.new-scannerScaffold a new vulnerability scanner implementation with tests following the project's existing pattern. Use when adding support for a new scanner tool.release-prepCheck version consistency, git tag status, and test results before cutting a release. Use when asked to prepare, validate, or check readiness for a release.
debug-running-instanceDebug a running instance of the notification-service controller. Use when investigating why notifications are not being sent, PipelineRuns are stuck with finalizers, or the controller pod is unhealthy.local-dev-setupSet up a local development environment to run and test the notification-service controller against a real Kubernetes cluster. Use when the user wants to deploy the controller locally, manually test PipelineRun reconciliation, or iterate on changes.run-testsRun unit tests, integration tests, and e2e tests for the notification-service controller. Use when the user asks to run tests, debug test failures, or wants to know how to execute a specific test.
building-and-testingUse when building the container image locally, running upstream tests, or linting. Covers submodule init, podman build, make test, and golangci-lint.ci-cd-quirksUse when CI checks fail unexpectedly, when modifying Tekton pipelines or GitHub Actions, or when debugging build failures. Covers pipeline structure, GitHub Actions scope, and image digest gotchas.updating-submoduleUse when updating the oauth2-proxy git submodule to a new upstream tag. Covers tag checkout workflow, version injection via ldflags, and commit conventions.
using-helpersUse when implementing task logic in release-service-utils and tempted to write a new utility function — check scripts/python/helpers/ first. Also use when working with Tekton results, HTTP, auth, file I/O, Pyxis, OSIDB, git, or subprocess wrappers.writing-new-task-scriptsUse when creating a new Python task script in release-service-utils, converting a Tekton task from release-service-catalog, adding scripts/python/tasks/ code, wiring Tekton params/results, or writing co-located pytest tests for a task.
add-template-fieldUse when konflux-ci/project-controller PRs add template-able fields in internal/template/resources.go, when users request parametrization of CR fields in ProjectDevelopmentStreamTemplate, when {{.var}} literals appear in generated…local-dev-setupUse when deploying or iterating on konflux-ci/project-controller against a local Konflux Kind cluster, when verifying template reconciliation end-to-end, when make run or make deploy against kind-konflux is needed, or when troubleshooting project-controller…