Review code changes for bugs and alignment with OpenEnv principles and RFCs. Use when reviewing PRs, checking code before commit, or when asked to review changes. Implements two-tier review model.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Review code changes for alignment with OpenEnv principles using a two-tier model.
Run automated checks first:
bash .claude/hooks/lint.sh - capture lint issuesbash .claude/hooks/check-debug.sh - capture debug codeRead alignment documents:
.claude/docs/PRINCIPLES.md - design principles.claude/docs/INVARIANTS.md - system invariantsRead open RFCs:
rfcs/ directory for all RFC filesAnalyze changes (use git diff or provided diff):
These are issues to fix without human input:
For each potential alignment concern, format as:
**ALIGNMENT FLAG**: [Brief description]
- **Principle/RFC at stake**: [Which principle from PRINCIPLES.md or RFC number]
- **The concern**: [What seems misaligned or in conflict]
- **Suggested reviewer**: @darktex [pull actual reviewers based on authors of the specific line of PRINCIPLES.md and INVARIANTS.md using git blame, and/or authors of conflicting RFCs]
Principle conflicts:
RFC conflicts (flag even for Draft/In Review RFCs):
Why flag RFC conflicts? Even if an RFC isn't finalized, flagging conflicts helps focus design discussions. The change might be correct and the RFC might need updating, or vice versa - either way, the team should discuss.
## Alignment Review Report
### Automated Checks
- Lint: [PASS/FAIL] - [summary]
- Debug code: [CLEAN/FOUND] - [details]
### Open RFCs Context
[List any RFCs in Draft or In Review status that might be relevant to these changes]
### Tier 1: Fixes Required
- [ ] path/file.py:123 - [issue description]
- [ ] path/file.py:456 - [issue description]
### Tier 2: Alignment Discussion
#### Principle Conflicts
[ALIGNMENT FLAGS for principle violations, or "None identified"]
#### RFC Conflicts
[ALIGNMENT FLAGS for RFC conflicts, or "None identified"]
### Summary
- X mechanical issues to fix
- Y alignment points for human review
- Z RFC conflicts to discuss
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Deploy an OpenEnv environment to Hugging Face Spaces. Use when asked to deploy, push to Hugging Face, or update a space.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Diagnose and recover failing or stuck Hugging Face Space deployments for OpenEnv environments. Use when deploying envs from `envs/` to the Hub (`openenv` namespace with version suffixes), when Spaces are in `BUILDING`/`APP_STARTING`/`RUNTIME_ERROR`, or when release collections need to be reconciled after targeted redeploys.
The English summary is being prepared. Showing the original description.
Make tests pass. Invoke after /write-tests produces failing tests.
The English summary is being prepared. Showing the original description.
OpenEnv CLI (`openenv`) for scaffolding, validating, building, and pushing OpenEnv environments.
The English summary is being prepared. Showing the original description.