nemoclaw-maintainer-cut-release-tag

Automates semver release tagging and version string updates for NemoClaw.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes manual, error-prone steps when preparing and publishing semver releases by guiding maintainers to bump version strings, create release PRs or perform direct releases, create annotated release and latest tags, and verify tags on the remote repository.

Core Features & Use Cases

  • Delegates version updates and build/test automation to the repository bump script invoked via npm run bump:version so all package.json, blueprint, installer defaults, and docs links are consistently updated.
  • Supports a dry-run preview, a recommended PR-based workflow that opens a release branch and PR, and an optional direct mode that commits to main and pushes annotated tags.
  • Provides step-by-step tagging instructions, explicit confirmation gates, and verification commands to ensure annotated tags and the floating latest tag point to the intended origin main commit.
  • Use Case: Maintainers preparing a release after CI has passed can use this Skill to produce a release PR, or skip the PR for urgent direct tagging while preserving safeguards.

Quick Start

Run the skill to bump the patch version, open a release pull request, and prepare annotated and latest tags for origin main.

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 automate creating a semver release tag and bumping version strings?

Automating a semver release tag and version string bump is handled by invoking the repository bump script via npm run bump:version, which updates package.json and docs before creating annotated git tags.

What is the safest way to cut a git release tag directly to main?

The safest way to cut a git release tag directly to origin main is by using the direct mode, which enforces explicit user confirmation gates and remote verification commands before pushing annotated tags.

Do I need git push access and Node.js to run the version bumping workflow?

Yes, you need git push access to origin, Node.js, and npm to run the bump-version script, prepare release pull requests, and push annotated release tags to the remote repository.

Can I preview a version bump and release tag before applying changes?

Yes, you can preview a version bump and release tag before applying changes by using the Skill's dry-run mode, which displays pending version string updates and tagging actions without modifying the repository.

How does the PR-based release workflow handle annotated and latest tags?

The PR-based release workflow handles annotated and latest tags by opening a release branch, bumping the version via npm, and providing step-by-step instructions to ensure both tags point to the intended origin main commit.

When should I avoid direct tagging and use a release pull request instead?

You should avoid direct tagging and use a release pull request for standard releases after CI passes, reserving direct mode only for urgent releases while still preserving explicit confirmation gates and remote verification.