draft-release-notes
/draft-release-notes
Compare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
- Author
- dawsonblock ↗
- Repository
- nemo ↗
- Licence
- Apache-2.0
- Last repository change
- 18.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/collect_release_evidence.py
What it does and when to use it
Compare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
Original author description
Compare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
How it works
- Gather Evidence
- Workflow
- Validate
SKILL.md preview
---
name: draft-release-notes
description: Compare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
---
# Draft Release Notes
Draft the three documentation-site release-notes pages from verified repository
evidence. Keep complete, PR-by-PR release history in GitHub Releases.
## Gather Evidence
Run the read-only helper with explicit release refs and the target minor version:
```bash
python3 .agents/skills/draft-release-notes/scripts/collect_release_evidence.py \
--previous release/<previous-major>.<previous-minor> \
--current HEAD \
--version <major>.<minor>
```
The report verifies both refs, compares their release-notes trees, identifies
version text currently present in those pages, and groups commits into review
candidates. Treat the groups as an evidence index, not publication-ready copy.
## Workflow
1. Confirm the target release version from the release branch and package
metadata. Preserve unrelated working-tree changes.
2. Run the helper. It reports an absent prior release-notes directory without
failing, which is expected for early release branches.
3. Verify each candidate claim in the changed public docs, API types, command
help, or source before including it. Prioritize breaking changes, migrations,
user-visible features, and ongoing support limitations.
4. Update only these pages unless the release changes their route or entry
points:
- `docs/about-nemo-relay/release-notes/index.mdx`
- `docs/about-nemo-relay/release-notes/highlights.mdx`
- `docs/about-nemo-relay/release-notes/known-issues.mdx`
5. Keep the existing page roles:
- `index.mdx` gives the current-release summary, compatibility notes, scope,
and curated feature links.
- `highlights.mdx` groups notable changes by user-facing theme.
- `known-issues.mdx` records current limitations, compatibility migrations,
current-release fixes, and the complete fixed-item history recorded in
earlier release-note pages. Preserve every prior fixed-item bullet under
release-labelled subsections; do not summarize, deduplicate, or omit it.
GitHub Releases remains the complete PR-by-PR history.
6. Preserve MDX front matter and the JSX SPDX comment. State the full history
is available in GitHub Releases; do not create a changelog or GitHub Release
body from this skill.
## Validate
Run the helper for the target release and for an early branch without release
notes when available. Review public claims, then run:
```bash
git diff --check
just docs
just docs-linkcheck
```
Check product names, commands, package names, support claims, and links against
the current repository before handing off the draft.
Files in this package (2)
- SKILL.md 3 KB
- scripts/collect_release_evidence.py 7 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · dawsonblock/nemo | 100 | Apache-2.0 |
| rommapp/romm | 100 | AGPL-3.0 |
| omnigent-ai/omnigent | 100 | Apache-2.0 |
| microsoft/agent-framework | 100 | MIT |
| nvidia/nemo-fabric | 100 | Apache-2.0 |
| nvidia/nemo-relay | 100 | Apache-2.0 |
| prisma/orm | 100 | Apache-2.0 |
| prisma/prisma-next | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version e66cba158fb1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90release-notes
Builds release notes from merged pull requests and git history. Use when the user asks for release notes, a changelog, or a summary of changes between versions. - 100create-release-notes
Generate user-facing release notes when the user asks to write release notes, document a release, summarize changes for users, or prepare a changelog between versions - 100test-go-binding
Build and test the NeMo Relay Go binding; use this for go/nemo_relay changes or Go-facing integration checks - 100release-notes
Generate release notes or changelog entries for completed changes. Use when asked to \"write release notes\", \"update the changelog\", \"document what changed\", \"create a release summary\", or when preparing a release. Follows Keep a Changelog format. - 100hf-release-notes
Generate Hugging Face Hub (huggingface_hub) release notes from cached PR JSON files. Use when asked to draft release notes from PR files. - 90dev10x:release-notes
Generate JTBD-driven release notes from git commits between releases. Playbook-powered workflow with configurable ticket patterns, output targets, and categories. TRIGGER when: preparing a release and need to generate changelog or release notes from commit history. DO NOT…