Nemoclaw Maintainer Evening
Complete the NemoClaw end-of-day documentation and release handoff.
Install
npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-evening -g -a claude-code -y- Repository
- NVIDIA/NemoClaw22.9k
- Category
- Writing
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 1,205 tokens
- Runs scripts
- No, instructions only
What it does
Complete the NemoClaw end-of-day documentation and release handoff. Cut a release tag only when requested.
NemoClaw Maintainer Evening
Close the day with one release candidate, one cumulative documentation change, and a clear handoff. Tagging is optional. Report tag creation first, then let the tag skill finish post-tag follow-through.
See PR-REVIEW-PRIORITIES.md for the daily cadence and the release-train policy for release rules.
1. Select the Target Version
Use the maintainer's vX.Y.Z when supplied. Otherwise, read the current target and show its
merged and open work:
node --no-warnings \
.agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts
node --no-warnings \
.agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts vX.Y.Z
Do not silently convert the answer into a patch, minor, or major bump. If nothing shipped, ask whether to stop without a tag.
2. Finish One Cumulative Documentation Change
Start the release kickoff checks for the intended range. Report independent prerequisites together, and continue authorized docs preparation and review during image waits. These preliminary reads do not select the tag candidate.
Inspect the current Docs / Author Post-Merge Catch-Up state. The Pi workflow owns documentation catch-up
for merged changes. Continue its managed draft PR when one exists. If no managed PR exists and the
release entry is the only missing change, use one direct documentation-only PR.
