القائمة
Flag identifiers whose name does not describe exactly what they contain — drift from package patterns, contradictory contents, misnamed feature gates, asymmetric mirror fields.
التثبيت باستخدام 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 | imprecise-names |
| description | Flag identifiers whose name does not describe exactly what they contain — drift from package patterns, contradictory contents, misnamed feature gates, asymmetric mirror fields. |
| license | Apache-2.0 |
| metadata | {"copyright":"The Kubernetes Authors"} |
Imprecise names — every new identifier must describe exactly what it contains. A reader should not be able to mistake it for something broader or narrower.
AddLabel(k, v) when the rest of the package uses Label(k, v)).noMoreBorrowingCohorts that actually contains cohorts which are still borrowing.SkipFinalizersForServingWorkloads that controls a different condition is a hard
naming violation.excludeResourcePrefixes exists, the
complement must be includeResourcePrefixes, not a freshly invented name.