huggingface/OpenEnv.
15 skills★ 2,729View on GitHub ↗
- 100/100
alignment-review
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.
- 80/100
deploy-hf
Deploy an OpenEnv environment to Hugging Face Spaces. Use when asked to deploy, push to Hugging Face, or update a space.
- 90/100
generate-openenv-env
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.
- 85/100
hf-space-recovery
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.
- 100/100
implement
Make tests pass. Invoke after /write-tests produces failing tests.
- 100/100
openenv-cli
OpenEnv CLI (`openenv`) for scaffolding, validating, building, and pushing OpenEnv environments.
- 100/100
pre-submit-pr
Validate changes before submitting a pull request. Run comprehensive checks including lint, tests, alignment review, and RFC analysis. Use before creating a PR, when asked if code is ready for review, or before pushing for PR.
- 100/100
release
Release workflow for deploying OpenEnv environments to Hugging Face Spaces and keeping canonical references in sync.
- 100/100
rfc-check
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
- 100/100
simplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
- 100/100
sprint
Work on a batch of GitHub issues in parallel using Agent Teams. Creates one worktree per issue with TDD enforcement, coordinates via a lead agent, then produces stacked PRs.
- 100/100
update-docs
Update documentation across the repo after API changes. Finds stale references in docs, examples, docstrings, and fixes them.
- 100/100
watch-pr
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.
- 100/100
work-on-issue
Start work on a GitHub issue. Extracts requirements, creates worktree, sets up TDD workflow.
- 100/100
write-tests
Write failing tests from requirements. Invoke for each todo before /implement.