nemoclaw-maintainer-cut-release-tag

Creates signed semver release tags on origin/main with E2E evidence verification and announcement drafting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cutting a NemoClaw release involves many error-prone manual steps: verifying changelog entries, gathering E2E evidence, creating signed tags, waiting for workflows, retiring labels, and drafting announcements. This Skill enforces a deterministic, script-driven release process that prevents mistakes like tagging the wrong commit or skipping required test evidence. ## Core Features & Use Cases - Deterministic Release Planning: Generates a release plan capturing the exact origin/main commit, next semver tag, and confirmation phrase before any tag is created. - E2E Evidence Gating: Builds an evidence ledger from workflow runs, requiring green test results or explicit maintainer exceptions before the tag is cut. - Workflow-Managed Housekeeping: Waits for the release-latest-tag workflow to move latest, carry open issues/PRs forward, and retire the released label. - Announcement Drafting and Verification: Generates release-note data and a Markdown draft, then verifies the maintainer-published GitHub Discussion before handoff. - Use Case: A maintainer says "cut release v0.0.58" and the Skill walks through plan generation, evidence collection, signed tag creation, label retirement, and announcement verification step by step. ## Quick Start Ask the agent to cut a new NemoClaw release, for example by saying "cut release v0.0.58 from origin/main", and follow the guided checklist through confirmation and announcement verification.

Frequently Asked Questions about nemoclaw-maintainer-cut-release-tag

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

FAQPage Schema
How do I cut a NemoClaw release tag?

Run npm run release:plan with a patch, minor, or major bump to generate a plan, gather E2E evidence for the candidate commit, then run npm run release:cut with the maintainer's confirmation phrase. Never run raw git tag or git push commands manually.

What E2E evidence is required before tagging a release?

Every test required by the e2e.yaml workflow at the candidate SHA must have green evidence, including the Exact staging Brev Launchable job, or an itemized maintainer exception. The evidence ledger is built with npm run release:e2e-evidence from a manifest of run, job, and dispatch receipt files.

Can I move the latest or lkg tags manually during a release?

No. The release-latest-tag workflow moves latest to the verified tag object automatically, and release admins promote lkg manually after validation. The Skill only pushes the semver tag and never touches latest or lkg.

What happens if origin/main moves after the release plan is generated?

All candidate-bound evidence is discarded, the plan is regenerated for the new origin/main SHA, and preflight plus all required E2E groups are rerun. A new confirmation phrase matching the new commit is required before cutting the tag.

Who publishes the GitHub release announcement?

The maintainer publishes the drafted release notes as a Discussion in the Announcements category. The Skill only drafts the Markdown locally and verifies the published Discussion URL, title, category, and links afterward.