update-docs
/update-docs
Find and fix stale documentation after API changes.
EXECUTE THESE STEPS NOW
When this skill is invoked, you MUST execute these steps immediately.
Step 1: Identify Changed Files
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:
More from meta-pytorch/openenv
write-tests
Write failing tests from requirements. Invoke for each todo before /implement.
25simplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
20alignment-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.
20pre-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.
20rfc-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.
19implement
Make tests pass. Invoke after /write-tests produces failing tests.
17