القائمة
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate OpenEnv environments from a concrete use case (for example, "generate an env for the library textarena"). Use when asked to design or implement a new environment under envs/ by researching a target library/API, selecting matching OpenEnv examples, asking key implementation questions, and building models/client/server/openenv.yaml. Do not use for model training or evaluation tasks.
Release workflow for deploying OpenEnv environments to Hugging Face Spaces and keeping canonical references in sync.
Hugging Face Hub CLI (`hf`) for downloading, uploading, and managing repositories, models, datasets, and Spaces on the Hugging Face Hub. Replaces now deprecated `huggingface-cli` command.
OpenEnv CLI (`openenv`) for scaffolding, validating, building, and pushing OpenEnv environments.
Deploy an OpenEnv environment to Hugging Face Spaces. Use when asked to deploy, push to Hugging Face, or update a space.
Monitor a PR's CI checks and Greptile code review after submission. Polls CI status, auto-fixes failures via ralph-loop, waits for Greptile review, addresses comments, and iterates until green.
| name | rfc-check |
| description | Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed. |
| allowed-tools | Read, Grep, Glob |
Determine if proposed changes require an RFC (Request for Comments).
Identify changed files using git diff --name-only or provided context
Apply RFC criteria:
RFC Required:
src/openenv/core/RFC Not Required:
Check against existing RFCs in rfcs/ for conflicts or dependencies
src/openenv/core/## 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]
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]