nemoclaw-maintainer-release-notes

Drafts post-tag NemoClaw release announcements from live GitHub tag and compare data.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-release-notes-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-release-notes
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-release-notes
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-release-notes-army161

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a release announcement after cutting a tag requires manually gathering commits, PR metadata, and contributor information from GitHub, then organizing it into a consistent narrative format. This Skill automates that drafting process using live GitHub data. ## Core Features & Use Cases - Live Data Collection: Queries the GitHub compare API and PR metadata via gh to build the shipped-change surface between two release tags. - Structured Announcement Drafting: Produces three narrative lead paragraphs, categorized shipped changes, why-it-matters bullets, and visible #NNNN PR links following the NemoClaw house style. - External Contributor Credit: Detects external contributors via GitHub org membership checks and handles replayed PRs by crediting original authors. - Use Case: After cutting the v0.0.x release tag, a maintainer asks for the announcement draft and receives a local Markdown file ready to paste into GitHub Discussions. ## Quick Start Draft the NemoClaw release announcement for the current tag using live GitHub compare and PR data.

Frequently Asked Questions about nemoclaw-maintainer-release-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a GitHub release announcement from tag compare data?

Run this Skill after cutting the release tag. It uses gh api compare between the previous and current tags, collects PR metadata for each shipped change, and writes a local Markdown draft with narrative paragraphs and categorized changes.

What format does the NemoClaw release announcement follow?

The announcement has three narrative lead paragraphs, 4-6 categorized sections of shipped changes, one why-it-matters bullet per change with visible #NNNN PR links, and an external-only contributor thanks section.

Does this Skill create the GitHub Discussion automatically?

No. It only creates a local Markdown draft outside the repository checkout. The maintainer manually creates the GitHub Discussion and pastes the draft content.

How are external contributors identified for release thanks?

The Skill checks each GitHub login against the NVIDIA org members API. A 404 response means the account is external and eligible for thanks; replayed PRs credit the original external author by username only.

What happens if the changelog entry is missing for the release tag?

The Skill reports the release-process defect and routes recovery through the nemoclaw-contributor-update-docs workflow. It never creates or silently repairs docs/changelog entries from the post-tag announcement flow.