Back to Details

nemoclaw-maintainer-day

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

NemoClaw Maintainer Day

NemoClaw 维护者日间流程

Execute one pass of the maintainer loop, prioritizing version-targeted work.
Autonomy: push small fixes and approve when gates pass. Never merge. Stop and ask for merge decisions, architecture decisions, and unclear contributor intent.
执行一轮维护者循环，优先处理版本目标相关工作。
自主性： 推送小型修复，在闸门校验通过时批准PR。绝不直接合并。遇到合并决策、架构决策或贡献者意图不明确的情况时，停止操作并询问用户。

References

参考文档

  • PR review priorities: PR-REVIEW-PRIORITIES.md
  • Risky code areas: RISKY-AREAS.md
  • State schema: STATE-SCHEMA.md
  • PR评审优先级：PR-REVIEW-PRIORITIES.md
  • 高风险代码区域：RISKY-AREAS.md
  • 状态 schema：STATE-SCHEMA.md

Step 1: Check Version 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.
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: Pick One Action

步骤2：选择一项操作

From the open version-targeted items, pick the highest-value one:
  1. Ready-now PR — green CI, no conflicts, no major CodeRabbit, has tests → follow MERGE-GATE.md
  2. Salvage-now PR — close to ready, needs small fix → follow SALVAGE-PR.md
  3. Security item — touches risky areas → follow SECURITY-SWEEP.md
  4. Test-gap item — risky code with weak tests → follow TEST-GAPS.md
  5. Hotspot cooling — repeated conflicts → follow HOTSPOTS.md
  6. Sequencing needed — too large for one pass → follow SEQUENCE-WORK.md
If all version-targeted items are blocked, fall back to the general backlog. Productive work on non-labeled items is better than waiting.
Prefer finishing one almost-ready contribution over starting a new refactor.
从所有标记了版本目标的待处理事项中，挑选最高价值的一项：
  1. 可立即处理的PR — CI校验通过、无冲突、无CodeRabbit重大提示、包含测试 → 遵循MERGE-GATE.md
  2. 可挽救的PR — 接近完成，仅需小型修复 → 遵循SALVAGE-PR.md
  3. 安全相关事项 — 涉及高风险代码区域 → 遵循SECURITY-SWEEP.md
  4. 测试缺口事项 — 高风险代码但测试薄弱 → 遵循TEST-GAPS.md
  5. 热点降温 — 反复出现冲突 → 遵循HOTSPOTS.md
  6. 需要任务排序 — 工作量过大无法单次完成 → 遵循SEQUENCE-WORK.md
如果所有版本目标相关事项都被阻塞，则退回到通用待办事项列表。处理未标记的事项也比等待更有成效。
优先完成接近就绪的贡献，而非启动新的重构工作。

Step 3: Execute

步骤3：执行操作

Follow the chosen workflow document. A good pass ends with one of:
  • a PR approved, a fix pushed, a test gap closed, a hotspot mitigated, or a blocker surfaced.
遵循选定的工作流文档。一轮有效的循环应达成以下成果之一：
  • PR获得批准、推送修复、填补测试缺口、缓解热点问题，或发现阻塞点。

Step 4: Report Progress

步骤4：汇报进度

Re-run the progress script and show the update:
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>
If all version-targeted items are done, suggest running 
/nemoclaw-maintainer-evening
early.
Update 
.nemoclaw-maintainer/state.json
via the state script:
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts history <action> <item> "<note>"
重新运行进度脚本并展示更新：
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>
如果所有版本目标相关事项均已完成，建议提前运行
/nemoclaw-maintainer-evening
。
通过状态脚本更新
.nemoclaw-maintainer/state.json
：
bash
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts history <action> <item> "<note>"

Commit Hygiene

提交规范

The prek "Regenerate agent skills from docs" hook auto-stages 
.agents/skills/
files. Before every 
git add
and 
git commit
on a PR branch, run 
git reset HEAD .agents/skills/nemoclaw-maintainer-*
to unstage them. Only commit skill files in dedicated skill PRs.
"Regenerate agent skills from docs"预提交钩子会自动暂存
.agents/skills/
目录下的文件。在PR分支上执行
git add
和
git commit
之前，务必运行
git reset HEAD .agents/skills/nemoclaw-maintainer-*
来取消暂存这些文件。仅在专门的技能PR中提交技能文件。

Stop and Ask When

以下情况需停止并询问

  • Broad refactor or architecture decision needed
  • Contributor intent unclear and diff would change semantics
  • Multiple subsystems must change for CI
  • Sensitive security boundaries with unclear risk
  • Next step is opening a new PR or merging
  • 需要进行大规模重构或架构决策
  • 贡献者意图不明确，且代码变更会改变语义
  • 为了通过CI需要修改多个子系统
  • 涉及敏感安全边界且风险不明确
  • 下一步操作是创建新PR或合并PR

/loop Integration

/loop 集成

Designed for 
/loop 10m /nemoclaw-maintainer-day
. Each pass should produce compact output: what was done, what changed, what needs the user. Check 
state.json
history to avoid re-explaining prior context on repeat runs.
专为
/loop 10m /nemoclaw-maintainer-day
设计。每轮循环应生成简洁的输出：已完成的工作、变更内容、需要用户处理的事项。查看
state.json
的历史记录，避免在重复运行时重复解释之前的上下文。