nvidia/nemoclaw · Archived

nemoclaw-maintainer-morning

Runs the morning maintainer standup for NemoClaw.

First seen Apr 14, 2026

Installation

$ npx skills add nvidia/nemoclaw --skill nemoclaw-maintainer-morning

Summary

  • Runs the morning maintainer standup for NemoClaw.
  • Triages the backlog, determines the day's target version, labels selected items, surfaces stragglers from previous versions, and outputs the daily plan.
  • Use at the start of the workday.
  • Trigger keywords - morning, standup, start of day, daily plan, what are we shipping today.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from nvidia/nemoclaw · top by installs.

npx skills add nvidia/nemoclaw

Browse all from nvidia/nemoclaw

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 22.3K
License LICENSE
Default branch main
Open issues 484
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,348 B
  • docs SUMMARY.md 361 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

NemoClaw Maintainer Morning

Start the day: triage, pick a version target, label items, share the plan.

See [PR-REVIEW-PRIORITIES.md](../nemoclaw-maintainer-day/PR-REVIEW-PRIORITIES.md) for the daily cadence and review priorities.

Step 1: Determine Target Version and Stragglers

node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts

This fetches tags, computes the next patch version, and finds open items still carrying older version labels. Surface stragglers first — they indicate post-tag housekeeping was interrupted or an item slipped across multiple cycles. Decide whether to relabel them to today's target or defer them out of the daily release flow.

Step 2: Triage

Run the triage script to rank the full backlog:

node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts --approved-only

If too few results, run without --approved-only. The script fetches open PRs through gh, reads Project 199 Priority, enriches candidates with review, CI, file, and risky-area data, and applies the scoring model documented in [PR-REVIEW-PRIORITIES.md](../nemoclaw-maintainer-day/PR-REVIEW-PRIORITIES.md).

Also use find-review-pr to surface security PRs whose Project Priority is Urgent or High. Merge these into the candidate pool.

Step 3: Label Version Targets

Present the ranked queue to the user. After they confirm which items to target, label them:

gh label create "<version>" --repo NVIDIA/NemoClaw --description "Release target" --color "1d76db" 2>/dev/null || true
gh pr edit <number> --repo NVIDIA/NemoClaw --add-label "<version>"
gh issue edit <number> --repo NVIDIA/NemoClaw --add-label "<version>"

Step 4: Save State and Output the Plan

Pipe triage output into state:

node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts \
  | node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts set-queue

Output the daily plan:

Target Item Type Owner Next action
v0.0.8 #1234 PR @author Run merge gate
v0.0.8 #1235 Issue unassigned Needs PR

Include: total items targeted, how many are PRs vs issues, how many are already merge-ready.

Notes

  • This skill runs once at the start of the day. Use /nemoclaw-maintainer-day during the day to execute.
  • On a PR, the target version label activates daily release work; actual release inclusion requires that PR to be merged with the label at cutoff.
  • On an issue, the target version label is tracking or "needs PR" coordination only.
  • Stragglers from previous versions should be addressed first — they already slipped once.