nemoclaw-maintainer-release-notes

Drafts post-tag NemoClaw release announcements from GitHub tag, compare, and PR metadata.

22.3k|3.1k|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-release-notes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-release-notes
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-release-notes
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a public release announcement after tagging a NemoClaw version requires manually gathering compare data, PR metadata, and contributor information, which is slow and error-prone. This Skill automates that drafting process while enforcing the project's house style and disclosure rules.

Core Features & Use Cases

  • Release Range Verification: Confirms the current and previous semver tags against live remote state using git and the GitHub compare API.
  • Automated Change Collection: Pulls commit headlines, PR metadata, and file changes via gh api and gh pr view to build the shipped-change list.
  • House-Style Drafting: Produces a Markdown announcement with three narrative lead paragraphs, categorized change bullets with visible PR links, and external-only contributor thanks.
  • Use Case: After tagging NemoClaw v1.2.0, a maintainer asks the agent to draft the announcement; the Skill verifies the tag range, collects PR data, credits external contributors, and writes a local Markdown draft ready to paste into GitHub Discussions.

Quick Start

Ask the agent to draft the NemoClaw release announcement for the version you just tagged, for example v1.2.0.

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 NemoClaw release announcement after tagging?

Run this Skill after the release tag exists and the changelog entry is in place. It verifies the tag range with git ls-remote, collects compare and PR data via the gh CLI, and writes a local Markdown draft you can paste into GitHub Discussions.

What data sources does the release notes draft use?

It uses the GitHub compare API for the tag range, gh pr view for PR metadata, and the tagged commit's dated changelog entry as release context. It never drafts from memory and always uses live remote state.

Does this Skill publish the GitHub Discussion automatically?

No. The Skill only creates a local Markdown draft outside the repository checkout. The maintainer manually creates the GitHub Discussion and shares the announcement link.

How are external contributors credited in release notes?

The Skill checks each GitHub login against NVIDIA org membership via the API and thanks only external contributors by username. Replayed external PRs credit the original author, and affiliations are never mentioned unless explicitly requested.

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

The Skill does not create or repair docs/changelog entries. It reports the release-process defect and routes recovery through the nemoclaw-maintainer-evening workflow instead.