Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From rfc123-skills
Incorporates review feedback into an RFC body by reading unresolved threads, drafting a revised version, showing a diff, and committing changes after user approval.
npx claudepluginhub twixes/rfc123How this skill is triggered — by the user, by Claude, or both
Slash command
/rfc123-skills:propose-revisionThis 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 incorporate review feedback into a revised RFC body.
Drafts a new RFC from a one-paragraph brief, walking through Background → Proposal → Alternatives → Open questions, then opens a pull request via the RFC123 MCP server.
Guides writing RFCs for features, architecture, processes, deprecations, migrations, and standards with workflow: type selection, git research, required sections (summary, problem, solution, alternatives, risks), review management, decision logging, and git commit to docs/rfcs/. Use for proposals needing team buy-in on large changes.
Facilitates Request for Comments (RFC) process for technical proposals and design decisions. Supplies templates, ADR comparisons, best practices, and IETF-adapted guidance.
Share bugs, ideas, or general feedback.
Help the user incorporate review feedback into a revised RFC body.
The user says "revise the RFC", "rewrite section X", or "update the proposal based on the feedback". Also useful when an unresolved thread is asking for specific changes the user agrees with.
Read the RFC and threads. Call rfc123_get_rfc, rfc123_get_rfc_comments, and
rfc123_list_review_threads to gather context. Pay particular attention to
threads whose isResolved is false and isOutdated is false.
Decide scope. Ask the user: are we addressing a specific thread, a specific section, or "everything that's still open"? Don't try to rewrite the whole thing if scoping it tighter is possible.
Draft the revision in-line. Show the user the proposed new body as
markdown. Do not call rfc123_update_rfc_body yet.
Show a diff summary. Highlight what changed (added/removed/reworded). A 5-line "what changed" digest before the full body works well for long bodies.
Wait for user approval. Only call rfc123_update_rfc_body after the
user says go. Pass changeDescription — a one-line summary of the
revision (e.g. "Tighten security section; address @alice feedback") that
becomes the commit message. The footer is added automatically; don't add
it yourself. The response includes linesAdded/linesRemoved so you
can report the size of the change without re-reading.
Mention follow-ups. If the revision settles a previously-unresolved
thread, suggest also using the resolve-threads skill to close it out.