菜单
Search openshift/release step-registry for existing steps, workflows, and chains before creating new CI components. Use when adding tests, jobs, or step-registry entries, or when asked to find reusable pre/test/post components.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/openshift/release --skill step-finder命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Add a new step-registry step (ref YAML + commands.sh) in openshift/release. Use when creating a new CI step, atomic test action, or reusable ref component. Run step-finder first to avoid duplicates.
Check AKS Kubernetes version support status using the official AKS release status API and compare against versions configured in CI config files. Use whenever someone asks about AKS K8s version support, EOL dates, deprecation, or whether the configured AKS version is still GA. Also use when planning AKS K8s version upgrades — run this before using rhdh-aks-tests to make changes.
List AKS test entries in RHDH ci-operator config files and update the AKS Kubernetes version per branch. Use when listing e2e-aks tests, changing MAPT_KUBERNETES_VERSION for AKS, or checking which AKS K8s version each release branch uses.
基于 SOC 职业分类
正在显示 SKILL.md
| name | step-finder |
| description | Search openshift/release step-registry for existing steps, workflows, and chains before creating new CI components. Use when adding tests, jobs, or step-registry entries, or when asked to find reusable pre/test/post components. |
Search 4,400+ step-registry components before creating duplicates.
ref, chain, or workflowFrom repo root:
python3 .claude/scripts/step_finder.py "<query>" [--type step|workflow|chain|all] [--show-usage] [--no-reverse-deps] [--limit N]
Examples:
python3 .claude/scripts/step_finder.py "aws upgrade" --type workflow
python3 .claude/scripts/step_finder.py "install operator" --type step --show-usage
python3 .claude/scripts/step_finder.py openshift-e2e-test --no-reverse-deps
All query tokens must match (name, path, or documentation).
*-commands.sh for top matches — do not guess behavior.ci-operator/config/<org>/<repo>/:
- ref: <name>- chain: <name>workflow: <name>make updatemake validate-step-registry and make checkconfig| Type | Files | Config reference |
|---|---|---|
| step | *-ref.yaml + *-commands.sh | ref: |
| chain | *-chain.yaml | chain: |
| workflow | *-workflow.yaml (pre/test/post) | workflow: |
Always run this skill before adding step-registry files. If a close match exists, extend it with env vars or compose it in a chain/workflow instead of copying.