Use when reviewing, auditing, or sanity-checking rook (github.com/rook/*) code, tests, docs, or workflows — a working tree, branch, commit range, or PR; when checking a branch before opening a PR; when reviewing, critiquing, or stress-testing a rook design…
Use when authoring or shepherding changes to rook (github.com/rook/*) repos — committing, pushing branches, opening or updating PRs, weighing review feedback, backporting, regenerating CRDs or generated code, writing tests or GitHub Actions workflows,…
Use when taking over, adopting, or superseding a rook (github.com/rook/*) pull request — an author who abandoned it, stopped responding to change requests, or produced an AI-burst PR whose substance is still worth landing. Covers both approaches: editing the…
Use when triaging rook (github.com/rook/*) issues or PRs — grooming or clearing the backlog, labeling or categorizing issues, finding duplicate issues, cross-linking an issue to a PR (or a PR to the issue it fixes), checking what info a bug report is missing,…
Use when applying one systemic change across a rook (github.com/rook/*) repo as a series of small, well-contained, independently reviewable PRs — dead-code elimination, lint/staticcheck cleanups, API migrations, renames, import or dependency hygiene. Triggers…