nemoclaw-maintainer-evening
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseNemoClaw Maintainer Evening
NemoClaw维护者晚间流程
Wrap up the day: check progress, bump stragglers, summarize for QA, cut the tag.
See PR-REVIEW-PRIORITIES.md for the daily cadence.
完成当日收尾工作:检查进度、调整滞后项、为QA生成总结、创建发布标签。
查看PR-REVIEW-PRIORITIES.md了解日常工作节奏。
Step 1: Check Progress
步骤1:检查进度
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>The first script determines the target version. The second shows shipped vs open. Present the progress summary to the user.
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>第一个脚本用于确定目标版本,第二个脚本展示已交付项与未完成项的情况。向用户展示进度总结。
Step 2: Bump Stragglers
步骤2:调整滞后项
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/bump-stragglers.ts <version> <next-version>This creates the next version label if needed, then moves all open items from the current version to the next. Tell the user what got bumped.
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/bump-stragglers.ts <version> <next-version>该脚本会在需要时创建下一版本标签,然后将当前版本的所有未完成项移至下一版本。告知用户哪些项被调整。
Step 3: Generate Handoff Summary
步骤3:生成交接总结
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/handoff-summary.tsThis lists commits since the last tag, identifies risky areas touched, and suggests QA test focus areas. Format the output as a concise summary the user can paste into the tag annotation or a handoff channel.
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/handoff-summary.ts该脚本会列出上次标签创建后的所有提交,识别涉及的风险区域,并建议QA测试的重点方向。将输出格式化为简洁的总结,方便用户粘贴到标签注释或交接频道中。
Step 4: Cut the Tag
步骤4:创建发布标签
Load . The version is already known — default to patch bump, but still show the commit and changelog for confirmation.
cut-release-tag加载工具。版本信息已确定——默认采用补丁版本更新,但仍需展示提交记录和变更日志供确认。
cut-release-tagStep 5: Confirm and Share
步骤5:确认并分享
After the tag is cut, present the final summary:
- Tag: at commit
v0.0.8abc1234 - Shipped: 4 items (#1234, #1235, #1236, #1237)
- Bumped to v0.0.9: 1 item (#1238 — still needs CI fix)
- QA focus areas: installer changes, new onboard preset
This summary can be shared in the team's handoff channel.
标签创建完成后,展示最终总结:
- 标签:,对应提交
v0.0.8abc1234 - 已交付项:4个(#1234、#1235、#1236、#1237)
- 移至v0.0.9的项:1个(#1238——仍需修复CI问题)
- QA重点区域:安装程序变更、新的预设配置
该总结可分享至团队的交接频道。
Step 6: Update State
步骤6:更新状态
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts history "tag-cut" "<version>" "shipped N items, bumped M"bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts history "tag-cut" "<version>" "shipped N items, bumped M"Notes
注意事项
- Never cut a tag without user confirmation.
- If nothing was labeled or nothing shipped, ask whether to skip the tag today.
- Version labels are living markers: they always mean "ship in this version." If an item slips, the label moves forward.
- 未经用户确认,切勿创建标签。
- 如果没有任何项被标记或没有交付任何内容,询问用户是否跳过今日标签创建。
- 版本标签是动态标记:它们始终代表“将在此版本中交付”。如果某项延迟,标签需向前调整。