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,…
Review MultiKueue changes for unnecessary reads from remote worker clusters.
Review Kueue enhancement proposals (KEPs) for project-wide design concerns and readability. Use when reviewing a new or updated KEP.
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.
Open or update Kueue pull requests and issues following the required templates, labels, titles, and AI disclosure rules.
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.
Flag unit or integration test function names that do not reflect the function or behavior under test.
Review a diff for naming precision, convention drift, reinvented helpers, log-verbosity mistakes, misaligned test names, and typos.