OpenParable
Skip to content
← Back to skills

Rfc Check

Productivity

Rfc Check is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Determine if proposed changes require an RFC.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/planning/rfc-check/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/rfc-check, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

RFC Check

Determine if proposed changes require an RFC (Request for Comments).

Instructions

  1. Identify changed files using git diff --name-only or provided context

  2. Apply RFC criteria:

    RFC Required:

    • New APIs in src/openenv/core/
    • Breaking changes to existing APIs
    • New abstractions or design patterns
    • Changes affecting the two-interface model (WebSocket/MCP separation)
    • Major architectural decisions

    RFC Not Required:

    • Bug fixes
    • Documentation updates
    • Minor refactoring (no API changes)
    • New example environments (unless introducing new patterns)
    • Dependency updates
    • Test additions
  3. Check against existing RFCs in rfcs/ for conflicts or dependencies

Analysis Steps

  1. List all files being changed
  2. Identify any files in src/openenv/core/
  3. Check for public API signature changes
  4. Look for new abstractions or patterns
  5. Review existing RFCs for related decisions

Output Format

## RFC Analysis

### Files Changed
- [list of files]

### Core Files Touched
- [any files in src/openenv/core/, or "None"]

### API Changes
- [any signature changes to public APIs, or "None"]

### New Patterns/Abstractions
- [any new patterns introduced, or "None"]

### Verdict: NOT REQUIRED / RECOMMENDED / REQUIRED

### Reasoning
[Explanation of decision based on criteria above]

### If RFC Needed
- Suggested title: "RFC NNN: [title]"
- Related RFCs: [list any related existing RFCs]
- Key decisions to document: [list]

RFC Template Reference

If an RFC is needed, use the template in rfcs/README.md:

# RFC NNN: Title

**Status**: Draft
**Created**: YYYY-MM-DD
**Authors**: @username

## Summary
[1-2 paragraph overview]

## Motivation
[Problem Statement + Goals]

## Design
[Architecture Overview, Core Abstractions, Key Design Decisions]

## Examples
[Code samples demonstrating usage]