nemoclaw-maintainer-morning

NemoClaw Maintainer Morning

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

See PR-REVIEW-PRIORITIES.md for the daily cadence and review priorities.

Step 1: Determine Target Version and Stragglers

node --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 --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.

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 --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts \
  | node --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts set-queue

Output the daily plan:

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.