菜单
Hard blocker — flag removal or relocation of code that manages cluster state owned by previous controller versions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build and manage a kind cluster for Workload-Aware Scheduling (WAS) e2e tests. Use when the user wants to set up, run tests against, or tear down a WAS test cluster built from Kubernetes main.
Flag solutions more elaborate than the problem requires — complexity that exists only because the author reached for a pattern.
Flag identical (or near-identical) blocks across types/adapters/call sites that should live in a shared helper — and newly extracted helpers with only one caller.
Flag code organization that a future maintainer will struggle to follow, modify, or extend.
Flag code put somewhere a reader would not expect to find it — cleanup scattered across callers, validation deep in business logic.
Flag unnecessary indirection, mismatched abstractions, or confusing data flow that obscures what the code is doing.
| name | deleted-backwards-compatibility-code |
| description | Hard blocker — flag removal or relocation of code that manages cluster state owned by previous controller versions. |
| license | Apache-2.0 |
| metadata | {"copyright":"The Kubernetes Authors"} |
Deleted backwards-compatibility code — this is a hard blocker. If the diff removes or relocates code that manages cluster state owned by previous versions (finalizer cleanup, annotation/label migration, ownership reconciliation, CRD field handling), think through a rolling upgrade: objects created by the old version must still be reconciled to a terminal state by the new version — finalizers removed, obsolete annotations dropped, status converged. Deleting finalizer-removal logic, for example, will leave pre-existing objects stuck forever.
