메뉴
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에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
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 직업 분류 기준
| 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.