菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/konflux-ci/tekton-tools --skill run-lints-and-tests命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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.
基于 SOC 职业分类
正在显示 SKILL.md
| name | run-lints-and-tests |
| description | 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. |
This repo has no unit tests. Validation consists of three locally-reproducible linters plus integration tests that run only in Konflux CI.
Matches CI exactly. Requires Python 3 and pipenv.
pipenv sync --dev
pipenv run yamllint .
Configuration: .yamllint -- disables line-length, key-ordering,
document-start/end; allows flexible list indentation (indent-sequences: whatever).
Ignores /vendor.
Validates commit messages against conventional commits format and requires a
Signed-off-by trailer.
pip install gitlint
gitlint --fail-without-commits --commits "origin/main..HEAD"
Configuration: .gitlint
| Rule | Requirement |
|---|---|
| Title format | Conventional commits (feat:, fix:, chore:, etc.) |
| Title length | Max 72 characters |
| Body line length | Max 72 characters |
| Body first line | Must be empty (blank line after title) |
| Signed-off-by | Required in body (git commit -s) |
Bot commits are auto-ignored (see the [ignore-by-author-name] regex in .gitlint
for the full list).
Validates Kubernetes manifests in config/ and tasks/.
kube-linter lint config/ tasks/ --config .kube-linter.yaml
Install from stackrox/kube-linter releases,
or use go install golang.stackrox.io/kube-linter/cmd/kube-linter@latest.
Configuration: .kube-linter.yaml -- only customization is excluding the latest-tag
check (dev deployment; production images are digest-pinned).
GitHub Actions enforces that AGENTS.md stays under 300 lines:
wc -l < AGENTS.md
This is checked by .github/workflows/lint.yaml on every PR.
Only rpms-signature-scan (in tasks/rpms-signature-scan/0.2/) is actively maintained.
The other two tasks are deprecated and pending removal:
tasks/generate-odcs-compose/tasks/provision-env-with-ephemeral-namespace/Do not invest effort linting or testing the deprecated tasks.
Integration tests run in Konflux via .tekton/rpms-signature-scan-tests-pull-request.yaml.
They cannot be run locally -- they require a Konflux cluster with Pipelines-as-Code.
The pipeline injects the PR's version of rpms-signature-scan via the PAC annotation:
pipelinesascode.tekton.dev/task: tasks/rpms-signature-scan/0.2/rpms-signature-scan.yaml
Three scenarios run against pinned test images in quay.io/vanguard_tests/:
| Scenario | Image | Expected RPMS_DATA |
|---|---|---|
| Signed RPMs | signed-rpms @ sha256:3ec7... | key 199e2f91fd431d51: 95, unsigned: 0 |
| Unsigned RPMs | unsigned-rpms @ sha256:076e... | key 199e2f91fd431d51: 163, unsigned: 68 |
| Image index | image_index @ sha256:da4f... | Aggregates both digests in IMAGES_PROCESSED |
Each scenario verifies:
TEST_OUTPUT contains "completed successfully" and "SUCCESS"RPMS_DATA matches expected signature key countsIMAGES_PROCESSED lists the correct digest(s)The test-container-pull-request pipeline runs all three linters (yamllint,
gitlint, kube-linter) plus builds the root container and runs rpms-signature-scan
against it. This is the main quality gate for PRs.
Before pushing a PR, run locally:
pipenv sync --dev && pipenv run yamllint .
gitlint --fail-without-commits --commits "origin/main..HEAD"
kube-linter lint config/ tasks/ --config .kube-linter.yaml
[ "$(wc -l < AGENTS.md)" -le 300 ] && echo "OK" || echo "AGENTS.md too long"