界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
效率与协作 · SKILL.md

nvidia-nemoclaw-maintainer-morning

nvidia-nemoclaw-maintainer-morning

【效率与协作】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.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: nvidia-nemoclaw-maintainer-morning description: 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. license: Apache-2.0 AND CC-BY-4.0 metadata: user_invocable: true author: NVIDIA

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 --experimental-strip-types --no-warnings .agents/skills/nvidia-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 — the team needs to decide: relabel to today's target, or defer further.

Step 2: Triage

Run the triage script to rank the full backlog:

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

If too few results, run without --approved-only. The script calls gh-pr-merge-now --json, enriches candidates with risky-area detection, and applies the scoring model documented in PR-REVIEW-PRIORITIES.md.

Also use find-review-pr to surface PRs with security + priority: high labels. 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/nvidia-nemoclaw-maintainer-day/scripts/triage.ts \
  | node --experimental-strip-types --no-warnings .agents/skills/nvidia-nemoclaw-maintainer-day/scripts/state.ts set-queue

Output the daily plan:

TargetItemTypeOwnerNext action
v0.0.8#1234PR@authorRun merge gate
v0.0.8#1235IssueunassignedNeeds 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.
  • The target version label is the source of truth for "what we're shipping today."
  • Stragglers from previous versions should be addressed first — they already slipped once.
我的收藏