Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By Twixes
Collaborate on engineering RFCs through the RFC123 MCP server — draft proposals from a brief, incorporate review feedback, resolve discussions with structured decision records, synthesize long threads into theme-grouped summaries, extract action items, and recommend reviewers based on file paths and team mappings.
npx claudepluginhub twixes/rfc123Use when an RFC discusses multiple options but hasn't laid them out side-by-side. Reads the body, extracts the alternatives, proposes comparison axes, builds a markdown table, and offers to commit it as a new section.
Use when the user wants to talk through a specific RFC in depth — understanding the proposal, pressure-testing it, comparing it against the actual codebase, and surfacing gaps the author missed. Pulls the RFC + threads via the MCP server, grounds the discussion in the current code, then takes the user's lead before posting anything back.
Use when the user wants to draft a new RFC from a one-paragraph brief. Walks them through Background → Proposal → Alternatives → Open questions, then opens the pull request via the RFC123 MCP server.
Use to surface explicit owner+action items buried in long RFC discussions ("@alice will write up the migration", "@bob to check with infra"). Posts a checklist comment so they're trackable.
Use when reviewers' feedback warrants a substantive edit to an RFC's body. Reads the RFC and unresolved threads, drafts a revised body, shows a diff for the user to approve, and commits via the RFC123 MCP server.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Governed workflow skills, reviewer agents, and enforcement hooks for govctl
Document intelligence - analyze docs, verify specs against implementation, and onboard to new areas via Glean. Requires glean-core.
GitHub and Git workflow tools: commit-creator, pr-creator, pr-reviewer, and pr-comment-resolver agents, slash commands for commits, PRs, and review comment resolution, plus skills for PR/commit workflows.
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in. Originally from OpenAI's curated skills catalog.
Git-as-knowledge-graph workflow for traceability across issues, branches, commits, reviews, and PRs.
UI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
The agent-native RFC platform for teams.
RFC123 is a collaborative platform for reviewing GitHub pull requests containing RFCs (Request for Comments). It provides a streamlined interface to view and discuss PR-based RFCs with powerful inline commenting capabilities on Markdown files.
http://localhost:3000 (for local development)http://localhost:3000/api/auth/callback/githubgit clone <your-repo-url>
cd rfc-123
pnpm install
Copy the example environment file:
cp .env.example .env.local
Edit .env.local and fill in the required values:
# GitHub OAuth App credentials
GITHUB_CLIENT_ID=your_github_oauth_app_client_id
GITHUB_CLIENT_SECRET=your_github_oauth_app_client_secret
# NextAuth configuration
# Generate with: openssl rand -base64 32
AUTH_SECRET=your_random_secret_here
# NextAuth URL (optional for local development)
# AUTH_URL=https://your-domain.com
# PostHog configuration (optional)
NEXT_PUBLIC_POSTHOG_KEY=your_posthog_project_api_key
NEXT_PUBLIC_POSTHOG_HOST=https://us.posthog.com
Generate your AUTH_SECRET:
openssl rand -base64 32
pnpm dev
Open http://localhost:3000 in your browser.
Update the target repository in src/lib/github.ts:
const owner = "your-org"; // Change to your GitHub org/user
const repo = "your-repo"; // Change to your repository name
RFCs should be markdown files (.md) located in a requests-for-comments/ directory in your repository's pull requests.
pnpm dev - Start development server on http://localhost:3000pnpm build - Create production buildpnpm start - Run production serverpnpm lint - Run Biome linterpnpm format - Format code with Biome