Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From rfc123-skills
Synthesizes long RFC discussions into structured summaries grouped by theme, distinguishing settled and unresolved points, and posts the roll-up as a comment.
npx claudepluginhub twixes/rfc123How this skill is triggered — by the user, by Claude, or both
Slash command
/rfc123-skills:synthesize-discussionThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Roll up a long RFC discussion into a short, structured summary that lets the
Walks through an RFC in depth — reads the proposal, grounds discussion threads, and current codebase to surface gaps, edge cases, and contradictions. Posts comments only on user request.
Clusters GitHub Discussions by recurring confusion themes, scores clusters by urgency, and drafts documentation fixes or content angles with verbatim quotes and source links.
Facilitates design discussions: researches RFC/ADR governance context via govctl, clarifies requirements, drafts RFCs/ADRs for spec phase handoff.
Share bugs, ideas, or general feedback.
Roll up a long RFC discussion into a short, structured summary that lets the author and new reviewers orient quickly.
The user says "synthesize the discussion", "summarize the comments", or "what are people arguing about?" on a specific RFC. Also worth offering proactively when an RFC has 20+ comments and the user is about to engage.
Read the RFC. Call rfc123_get_rfc so you understand what was proposed.
Read every comment and thread. Call rfc123_get_rfc_comments and
rfc123_list_review_threads in parallel. You need both: review threads carry the
resolved/unresolved state; general comments don't.
Group by theme. Cluster comments into 3–6 themes. A theme is a concern or topic, not a person. Examples: "migration risk", "naming", "scope of the change", "perf". Two unrelated points from the same person → two themes.
Within each theme, distinguish:
Cite people by @login. Specific attributions ("@alice flagged X,
@bob countered with Y") are more useful than passive voice. Don't include
the via-Claude footer of any prior bot comments in your tally.
Format the output. Use this template (adapt as needed):
## Discussion synthesis
### Theme 1: <name>
**Settled:**
- @alice raised X. Resolved by Y. (thread <link or short quote>)
**Unresolved:**
- @bob is pushing back on Z because <reason>. No response yet.
### Theme 2: <name>
…
Post it. Call rfc123_post_general_comment with the synthesis. The MCP
server appends the via-Claude footer automatically.