rfc-check Skill
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed. Published by huggingface in OpenEnv.
What is rfc-check Skill?
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed. Published by huggingface in OpenEnv. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Data analysis
- Design and media
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use rfc-check Skill
- Use it for testing.
- Use it for documentation.
- Use it for data analysis.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: huggingface
- Repository: huggingface/OpenEnv
- Skill file: .claude/skills/rfc-check/SKILL.md
What it does
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
Skill instructions
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
Explore related resources
Frequently asked questions
What is rfc-check?
rfc-check is a open-source AI agent skill with Copy skill directory. Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
Who is rfc-check best for?
rfc-check is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows, data analysis workflows.
How do I install rfc-check?
Install or run rfc-check using Copy skill directory. Check rfc-check for the latest setup command.
Is rfc-check actively maintained?
rfc-check may need a closer maintenance check before production use.
Auto-fetched from GitHub.
