Deleted Backwards Compatibility Code
Testing & Qualitydeleted-backwards-compatibility-codeDeleted Backwards Compatibility Code is an Agent Skill for testing & quality published in the kubernetes-sigs/kueue repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Hard blocker — flag removal or relocation of code that manages cluster state owned by previous controller versions.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/kubernetes-sigs/kueue/blob/HEAD/cmd/experimental/skills/reviewer/buggy-behavior/deleted-backwards-compatibility-code/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/deleted-backwards-compatibility-code, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Skill: Deleted Backwards-Compatibility Code
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.