// Review that new feature-gated behavior has explicit gate checks on all reachable code paths.
Write or review Kueue PR release notes. Use when a user asks to draft, refine, validate, or combine release notes for a Kueue pull request, especially when deciding whether the note should be framed as a bugfix, feature, observability improvement, or breaking change.
Review that algorithm comments match the implementation. Use when a comment describes a formula or algorithm and you want to verify it matches what the code actually does.
Review that new CRD fields have complete godoc comments with enum value descriptions.
Review that paired operations and fields that always appear together are encapsulated in a helper or nested struct.
Review that local variables with unnecessarily wide scope are extracted into helper functions.
Review that update/mutation logic has integration test coverage in test/integration/.
| name | feature-gated-code |
| description | Review that new feature-gated behavior has explicit gate checks on all reachable code paths. |
| license | Apache-2.0 |
| metadata | {"copyright":"The Kubernetes Authors"} |
Flag: New behavior that belongs to a feature gate (e.g., features.Enabled(features.SomeFeature)) but a reachable code path is missing the check — either the function has no early return when the gate is off, or a call site branches on other conditions without first checking the gate.
Ask: Add an explicit if !features.Enabled(features.SomeFeature) { return } short-circuit. Prefer placing it inside the function (so it's enforced for all current and future callers) over guarding every call site individually. If the check must live at the call site, document why.