rfc-check

Determine if proposed changes require an RFC by applying criteria and checking conflicts.

2.5k|421|Updated Oct 1, 2025
One-click install
npx skills add https://github.com/meta-pytorch/OpenEnv --skill rfc-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfc-check
Source: https://github.com/meta-pytorch/OpenEnv/tree/main/.claude/skills/rfc-check
Command: npx skills add https://github.com/meta-pytorch/OpenEnv --skill rfc-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This RFC Check Skill helps engineering teams determine whether proposed changes require an RFC before starting significant work, reducing misalignment and wasted effort.

Core Features & Use Cases

  • Assess whether changes introduce new APIs or breaking changes in the OpenEnv core and related modules.
  • Cross-reference against existing RFCs in rfcs/ to identify conflicts or dependencies.
  • Provide a clear decision rationale suitable for RFC submission and stakeholder communications.

Quick Start

Run the RFC check on your feature branch to determine RFC necessity. Provide the set of changed files, and the tool will indicate whether an RFC is required and summarize key considerations. Example: git diff --name-only origin/main...HEAD | rfc-check --input -

Frequently Asked Questions about rfc-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When do I need an RFC for code changes?

An RFC is required when changes introduce new APIs, breaking changes, or architectural decisions. RFC check evaluates your proposed changes against these criteria to determine RFC necessity before significant work begins, reducing misalignment and wasted effort.

How do I check if my changes require an RFC?

Provide your changed files to RFC check—typically via `git diff --name-only origin/main...HEAD`—and it assesses whether new APIs, breaking changes, or architectural decisions are involved, outputting a formal verdict with rationale.

Can RFC check detect conflicts with existing RFCs?

Yes. RFC check cross-references your proposed changes against existing RFCs in the rfcs/ directory to identify conflicts or dependencies, helping you align with prior architectural decisions.

What output does RFC check provide?

RFC check outputs a formal verdict on whether an RFC is required, plus a concise rationale summarizing key considerations—suitable for RFC submission and stakeholder communications.

Does RFC check work with breaking changes and API modifications?

Yes. RFC check specifically assesses whether changes introduce new APIs or breaking changes in the core and related modules, flagging those scenarios as RFC-required changes.

How does RFC check fit into the code review workflow?

Run RFC check on your feature branch before starting significant work. It integrates with git workflows to validate change scope early, preventing unnecessary development on changes that require RFC approval first.