Gym: Skill for Claude Code

NeMo Gym Release Notes

Write concise release notes that explain what users can now accomplish and why it matters.

Build an evidence base

1. Identify the previous release tag and exact release branch or commit.
2. Treat that bounded range as authoritative. Exclude changes outside it, regardless of branch.
3. Read the preceding release notes for structure, voice, bullet length, punctuation, and emphasis.
4. For each candidate, record the supporting commit or PR, user outcome, shipped scope, and intended section.
5. Verify contributor counts and first-time status from the same range, excluding bots.
6. Check ambiguous claims against the implementing PR, code, tests, and docs.
7. Distinguish a PR's motivating use case from the interface contract actually shipped.

Work in dependency order

1. Draft all detailed release-note sections.
2. Self-review every bullet with the checklist below, then reread the full draft for duplication, inconsistent terminology, misplaced items, weak priority, and contradictions.
3. Recheck corrected claims against the evidence base.
4. Derive the Release Summary and Highlights from the approved sections.
5. Update README news last as a condensed mirror of the approved Highlights.

Write for users

• Lead with the outcome; name the mechanism afterward.
• Replace implementation jargon with the task it enables, or define the term on first use.
• Omit command syntax unless it is essential to the user action; leave procedural details to the documentation.
• Explain unfamiliar environments or integrations instead of listing names alone.
• Give migrations enough context for users to understand what changed, whether they are affected, and what action to take.
• State safety or isolation limits explicitly. For example, host-process execution is not sandbox isolation.
• Describe only shipped support. Distinguish infrastructure for defining a capability from ready-made implementations, and provider-neutral architecture from providers that implement it.
• Keep documentation additions in a documentation section rather than presenting them as product capabilities.