From RFC123 Skills
Recommends RFC reviewers by analyzing file paths, prior commenters, and team mappings. Shows a ranked list with rationale, then requests reviewers on approval.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rfc123-skills:suggest-reviewersThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help the user pick the right reviewers for an RFC.
Help the user pick the right reviewers for an RFC.
The user just drafted an RFC and isn't sure who should review, or wants to add reviewers to an existing RFC.
Read the RFC. Call rfc123_get_rfc for the target RFC and note: the file
paths the PR touches, the author, and any reviewers already requested.
Look for adjacent context. Call rfc123_list_rfcs on the same repo. Scan for
prior RFCs that:
markdownFilePath).requestedTeamSlugs that match the topic area.Build a candidate list. For each candidate, write down the reason
they're a good fit ("authored related RFC #X about Y"; "is on
${org}/${team} which has reviewed every storage RFC"). Bare names with
no reason are not useful – the user can't sanity-check them.
Rank. Cap the list at 5 individuals + up to 2 teams. Rank by directness of relevance, not seniority.
Show the user. Surface the ranked list with reasons. Do not call
rfc123_request_reviewers yet.
Verify handles. Once the user picks who to request, run
rfc123_search_reviewers on any name you're uncertain about. The tool is
org-scoped (across orgs that host RFC repos visible to you) and returns
mixed users + teams with a kind discriminator and a ready-to-use
handle. For teams, handle comes back as org/slug.
Request. Call rfc123_request_reviewers with the chosen users and
teams. The response echoes back added, alreadyRequested, removed,
and the final pending set – share the relevant slice with the user. If
the user wants to swap a stalled reviewer, use removeUsers /
removeTeams in the same call.
requestedTeamSlugs
of any existing RFC, ask the user to confirm the team exists.npx claudepluginhub twixes/rfc123Walks through an RFC in depth, comparing the proposal against the actual codebase to surface gaps, edge cases, and contradictions the author missed. Stays in chat — never posts to GitHub.
Routes work to the right people using CodeScene ownership data. Connects files or directories to likely reviewers and domain experts.
Interactively responds to PR review feedback: fetches comments, verifies findings, asks for user approval, makes changes, and posts replies. Use when addressing GitHub pull request reviews.