Menu
Flag extra checks that are logically unreachable at the call site — they add noise and can mask future regressions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | unnecessary-guard-conditions |
| description | Flag extra checks that are logically unreachable at the call site — they add noise and can mask future regressions. |
| license | Apache-2.0 |
| metadata | {"copyright":"The Kubernetes Authors"} |
Unnecessary guard conditions — extra checks that are logically unreachable at the call site. They are a mild correctness concern: they add noise, suggest the author was uncertain about an invariant, and can mask a future regression that breaks the invariant they were silently relying on.
