All authors
Claude Skills by jhoblitt
github.com/jhoblitt5 skills0 installs0 views
- Rook Code ReviewUse 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 proposal, design doc, enhancement doc, or design/** change before it becomes code; when bulk-reviewing open rook PRs or evaluating a contributor's PRs for validity or security; for assert-vs-require audits; when drafting rook review comments.Votes: 0GitHub stars: 4
- Rook ConventionsUse 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, watching or retrying CI, or before ANY gh write (comment, label, close, edit) to a rook issue or PR.Votes: 0GitHub stars: 4
- Rook Pr TakeoverUse 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 existing PR's title and description in place, and opening a replacement PR that carries the commits forward with corrected messages, then closing the original. Triggers include "take over PR N", "adopt this PR", "supersede it". Judging wh...Votes: 0GitHub stars: 4
- Rook Systemic PrsUse 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 include: "sweep the rook repo for X", "break this into small PRs", "dead code elimination campaign", "iteratively clean up rook", "find another N PRs worth of <change>".Votes: 0GitHub stars: 4
- Rook TriageUse 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, deciding who should review a PR or requesting reviewers, or refreshing the routing knowledge base ("kb refresh"). Scope with "issues", "prs", or "both"; single items as "issue N" / "pr N". Deep code review routes to rook-code-review.Votes: 0GitHub stars: 4