nemoclaw-maintainer-triage
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->
NemoClaw Maintainer — Triage
NemoClaw 维护者 — 标签分类
AI-assisted label suggestion for issues and PRs. Reads live triage instructions, suggests labels and a triage comment, applies on approval, and logs the session.
用于Issues和PRs的AI辅助标签建议工具。读取实时分类指南,建议标签和分类评论,获得批准后应用,并记录会话。
Step 1: Read Triage Instructions
步骤1:阅读标签分类指南
Before suggesting any labels, read the live instructions from references/triage-instructions.md.
Do not triage from memory. The instructions contain the label guide, tone rules, skip list, and output format. They may have been updated since your last session.
在建议任何标签之前,请从references/triage-instructions.md读取最新指南。
不要凭记忆进行分类。该指南包含标签规则、语气规范、跳过列表和输出格式。自您上次会话以来,这些内容可能已更新。
Step 2: Determine Mode
步骤2:确定模式
Single-item mode — user provides a specific issue or PR number:
bash
undefined单条目模式 — 用户提供特定的Issue或PR编号:
bash
undefinedFor an issue:
针对Issue:
gh issue view <number> --repo NVIDIA/NemoClaw --json number,title,body,labels,url,author
gh issue view <number> --repo NVIDIA/NemoClaw --json number,title,body,labels,url,author
For a PR:
针对PR:
gh pr view <number> --repo NVIDIA/NemoClaw --json number,title,body,labels,url,author
**Batch mode** — user says "batch", "all unlabeled", or provides no number:
```bashgh pr view <number> --repo NVIDIA/NemoClaw --json number,title,body,labels,url,author
**批量模式** — 用户输入“batch”、“all unlabeled”或未提供编号:
```bashFetch unlabeled open issues (no labels applied yet):
获取未标记的开放Issue(尚未应用任何标签):
gh issue list --repo NVIDIA/NemoClaw --limit 50 --json number,title,body,labels,url,author
| jq '[.[] | select(.labels | length == 0)]'
| jq '[.[] | select(.labels | length == 0)]'
gh issue list --repo NVIDIA/NemoClaw --limit 50 --json number,title,body,labels,url,author
| jq '[.[] | select(.labels | length == 0)]'
| jq '[.[] | select(.labels | length == 0)]'
Fetch unlabeled open PRs:
获取未标记的开放PR:
gh pr list --repo NVIDIA/NemoClaw --limit 50 --json number,title,body,labels,url,author
| jq '[.[] | select(.labels | length == 0)]'
| jq '[.[] | select(.labels | length == 0)]'
In batch mode, work through items one at a time — present each suggestion and wait for approval before moving to the next.
---gh pr list --repo NVIDIA/NemoClaw --limit 50 --json number,title,body,labels,url,author
| jq '[.[] | select(.labels | length == 0)]'
| jq '[.[] | select(.labels | length == 0)]'
在批量模式下,逐个处理条目——展示每个建议并等待批准后再处理下一个。
---Step 3: Suggest Labels and Comment
步骤3:建议标签和评论
For each item, apply the rules from and present:
triage-instructions.mdAction: · Suggested labels: ,
Reason: One sentence from the instructions.
Triage comment (optional):
labelbugPlatform: MacOSComment text here.
Ask: "Apply these labels? (yes / skip / edit labels / no comment)"
Options:
- yes — apply as shown
- skip — move to next item without applying
- edit labels — user specifies different labels, then apply
- no comment — apply labels only, skip posting the comment
针对每个条目,应用中的规则并展示:
triage-instructions.md操作: · 建议标签: ,
理由: 来自指南中的一句话。
分类评论(可选):
labelbugPlatform: MacOS此处为评论文本。
询问:“是否应用这些标签?(yes / skip / edit labels / no comment)”
选项:
- yes — 按所示应用
- skip — 不应用,直接处理下一个条目
- edit labels — 用户指定其他标签后应用
- no comment — 仅应用标签,跳过发布评论
Step 4: Apply on Approval
步骤4:批准后应用
Apply labels:
bash
undefined应用标签:
bash
undefinedIssue:
Issue:
gh issue edit <number> --repo NVIDIA/NemoClaw --add-label "bug,Platform: MacOS"
gh issue edit <number> --repo NVIDIA/NemoClaw --add-label "bug,Platform: MacOS"
PR:
PR:
gh pr edit <number> --repo NVIDIA/NemoClaw --add-label "enhancement: inference"
Post comment (if approved):
```bash
gh issue comment <number> --repo NVIDIA/NemoClaw --body "Comment text here."gh pr edit <number> --repo NVIDIA/NemoClaw --add-label "enhancement: inference"
发布评论(如果获得批准):
```bash
gh issue comment <number> --repo NVIDIA/NemoClaw --body "此处为评论文本。"or for PRs:
或针对PR:
gh pr comment <number> --repo NVIDIA/NemoClaw --body "Comment text here."
---gh pr comment <number> --repo NVIDIA/NemoClaw --body "此处为评论文本。"
---Step 5: Log to Activity
步骤5:记录到活动日志
After each approved item, append to .
~/development/daily-rhythm/activity/nemoclaw-triage-log.mdUse the absolute path — this file lives in the daily-rhythm activity folder so it persists to GitLab over time.
markdown
undefined每个获批条目处理完成后,将内容追加到文件中。
~/development/daily-rhythm/activity/nemoclaw-triage-log.md使用绝对路径——该文件存储在daily-rhythm活动文件夹中,因此会长期同步到GitLab。
markdown
undefined[ISSUE|PR] NVIDIA/NemoClaw#<number> — <title>
[ISSUE|PR] NVIDIA/NemoClaw#<编号> — <标题>
Date: YYYY-MM-DD
Labels applied: bug, Platform: MacOS
Comment posted: yes | no
Create the file if it doesn't exist, with this header:
```markdown日期: YYYY-MM-DD
应用的标签: bug, Platform: MacOS
已发布评论: 是 | 否
如果文件不存在,请创建该文件并添加以下头部内容:
```markdownNemoClaw — Triage Log
NemoClaw — 标签分类日志
A running record of label triage actions on NVIDIA/NemoClaw issues and PRs.
Persisted via daily-rhythm to GitLab.
At the end of a batch session, append a session summary before the individual entries:
```markdown这是NVIDIA/NemoClaw的Issues和PR标签分类操作的持续记录
通过daily-rhythm同步到GitLab。
在批量会话结束时,在单个条目之前追加会话摘要:
```markdownYYYY-MM-DD — Triage Session
YYYY-MM-DD — 标签分类会话
Items triaged: N
Labels applied: N labels across N items
Never stage or commit this file to the NemoClaw repo.
---已分类条目数: N
已应用标签数: 共N个条目,总计N个标签
请勿将此文件暂存或提交到NemoClaw仓库。
---Response Time Note
响应时间说明
When triaging in batch mode, prioritize items in this order:
- Items with outage, data loss, or critical breakage signals in title or body (candidate for )
priority: high - Items opened by company-affiliated or known community contributors
- Issues open > 5 business days with no label (first-response window at risk)
- Everything else by recency
在批量模式下进行分类时,请按以下顺序优先处理条目:
- 标题或正文中包含服务中断、数据丢失或严重故障信号的条目(候选标签)
priority: high - 由公司关联人员或知名社区贡献者提交的条目
- 已开放超过5个工作日且未标记的Issues(可能超出首次响应窗口)
- 其余条目按创建时间排序(最新优先)