kubernetes-sigs/kueue

kueue-pr-issue-workflow

Open or update Kueue pull requests and issues following the required templates, labels, titles, and AI disclosure rules.

kueue-e2e-cluster-singlecluster

Create (or reuse) a single kind cluster for Kueue e2e development. Use when a user asks to spin up an e2e cluster, get a local kind environment ready for e2e tests, or debug/iterate against a single-cluster e2e suite (baseline, extended, sequential, TAS,…

multikueue

Review MultiKueue changes for unnecessary reads from remote worker clusters.

kep-review

Review Kueue enhancement proposals (KEPs) for project-wide design concerns and readability. Use when reviewing a new or updated KEP.

kep-writing

Write or revise a Kueue enhancement proposal (KEP) so maintainers can review it quickly. Use when drafting a new KEP, updating an existing one, or before opening or pushing a KEP pull request.

kueue-verify

Run Kueue's complete verification suite before pushing changes or opening or updating a pull request. Use as final validation to catch CI failures, including stale generated files.

misaligned-test-names

Flag unit or integration test function names that do not reflect the function or behavior under test.

code-style

Review a diff for naming precision, convention drift, reinvented helpers, log-verbosity mistakes, misaligned test names, and typos.

extract-helpers

Review that local variables with unnecessarily wide scope are extracted into helper functions.

integration-coverage

Review integration coverage of component interactions, event wiring, and API-server behavior.

split-test-files

Review that new feature tests are split into their own file rather than added to an already large test file.

table-driven-tests

Review reuse of suitable tables and setup for independent unit-test scenarios.

tests-run-in-ci

Review that tests added or changed by a PR are selected and run by at least one presubmit CI job.

visibility-exports

Review that newly exported functions have callers outside the package, lowercasing those that don't.

kueue-flake-debugger

Debug Kueue CI flakes. Use when a user asks to debug a flake, investigate a test failure, a test timeout, or a CI flake. Analyzes Prow build logs, CI Pod resources, Prometheus metrics, envtest lifecycle, kube-scheduler logs, kubelet logs, and test code to…

was-cluster

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.

kueue-release-notes

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…

kueue-go-lint

Run Kueue's Go linter after modifying Go code. Use before committing, pushing, opening or updating a pull request, or handing Go changes back to a user.

kueue-e2e-cluster-multikueue

Create (or reuse) the manager + worker kind clusters for Kueue MultiKueue e2e development. Use when a user asks to spin up MultiKueue e2e clusters, get a local multi-cluster environment ready, or debug/iterate against a MultiKueue e2e suite (baseline,…

avoidable-complexity

Flag solutions more elaborate than the problem requires — complexity that exists only because the author reached for a pattern.

duplicated-logic

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.

illogical-structure

Flag code organization that a future maintainer will struggle to follow, modify, or extend.

misplaced-logic

Flag code put somewhere a reader would not expect to find it — cleanup scattered across callers, validation deep in business logic.

nonsensical-decisions

Flag unnecessary indirection, mismatched abstractions, or confusing data flow that obscures what the code is doing.

pointless-intermediate-variables

Flag redundant local variables that add noise without adding clarity.

scope-creep

Flag diffs that bundle a bugfix with an unrelated refactor, or generalize a change to all types when only one type needs it.

architectural-decisions

Review a diff for small-scale structural problems — unjustified complexity, duplicated logic, scope creep, or misplaced code.

deleted-backwards-compatibility-code

Hard blocker — flag removal or relocation of code that manages cluster state owned by previous controller versions.

feature-gate-interaction-bugs

Flag feature-gated behavior whose gate-off path is incorrect — early returns that skip cleanup, or state set only when on but read unconditionally.

logic-errors

Flag incorrect conditionals, inverted boolean checks, off-by-one errors, unhandled edge cases, race conditions, or mishandled error returns.

buggy-behavior

Review a diff for behavioral defects — logic errors, broken edge cases, feature-gate bugs, and deletions that break backwards compatibility during rolling upgrades.

unnecessary-guard-conditions

Flag extra checks that are logically unreachable at the call site — they add noise and can mask future regressions.

code-eval

Evaluate the quality of a git diff between two commits by delegating per-skill analysis (Code Style, Buggy Behavior, Comments, Architectural Decisions, Security) to subagents, then aggregating their findings and recommendations into a scored report.

code-style-typos

Flag typos in identifiers, strings, or any text introduced by the diff.

convention-drift

Flag new code that breaks naming conventions already established in the same file or package.

imprecise-names

Flag identifiers whose name does not describe exactly what they contain — drift from package patterns, contradictory contents, misnamed feature gates, asymmetric mirror fields.

reinvented-helpers

Flag logic that duplicates an existing util/helper function instead of reusing it.

wrong-log-verbosity

Flag per-reconcile-cycle log lines emitted at V(2) — recurring reconcile-loop logs must be V(4) or higher.

comment-typos

Flag typos and obvious errors in comment text.

inaccurate-comments

Flag any comment or docstring that no longer matches the code — these mislead future maintainers who trust them.