Update documentation across the repo after API changes. Finds stale references in docs, examples, docstrings, and fixes them.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Find and fix stale documentation after API changes.
When this skill is invoked, you MUST execute these steps immediately.
Run:
git diff --name-only main...HEAD -- '*.py'
If no changes are found relative to main (e.g., on main or no upstream), fall back to:
git diff --name-only HEAD~1 -- '*.py'
If that also fails, ask the user which files changed.
Collect the list of changed Python files.
For each changed .py file, compare old vs new signatures using the same ref that worked in Step 1:
# If Step 1 used main...HEAD:
git diff main...HEAD -- <file>
# If Step 1 fell back to HEAD~1:
git diff HEAD~1 -- <file>
Look for changes to:
Build a list of (old_signature, new_signature) pairs.
If no API changes are found (only internal logic changes), report "No API changes detected — no docs update needed" and stop.
Use the Task tool to spawn the docs-updater agent. IMPORTANT: the
description field MUST contain "docs-updater" so the SubagentStop
hook fires correctly.
Task tool:
subagent_type: general-purpose
description: "docs-updater propagation"
prompt: |
You are a docs-updater agent. Read .claude/agents/docs-updater.md
for your full instructions.
Here are the API changes to propagate:
Changed files: <list>
API changes:
- `old` → `new`
...
Search the entire repo for references to the old APIs and update
them to match the new signatures. Follow the process in
.claude/agents/docs-updater.md exactly.
After the agent returns:
Report the summary to the user.
/implement when API signatures changed/pre-submit-pr to ensure docs are fresh/write-tests → Red (failing tests)
/implement → Green (passing tests)
/update-docs → Fix stale docs across repo ← THIS SKILL
/simplify → Refactor (optional)
/pre-submit-pr → Validate before PR
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.
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.
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.