Back to Details

triage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- markdownlint-disable MD013 -->
<!-- markdownlint-disable MD013 -->

Triage

问题分流

Move issues on the tracker through a small state machine of triage roles. A PR is an issue with attached code — same roles, same states, same machine.
The tracker and label vocabulary come from 
docs/agents/issue-tracker.md
; run 
bootstrap
if missing.
Every comment or issue an agent posts during triage must start with:
text
> *This was generated by AI during triage.*
将追踪器上的问题通过问题分流角色的小型状态机进行流转。PR是附带代码的问题——适用相同的角色、状态与状态机。
追踪器与标签词汇来自
docs/agents/issue-tracker.md
；若缺失请运行
bootstrap
。
Agent在分流过程中发布的每条评论或问题必须以以下内容开头：
text
> *This was generated by AI during triage.*

Roles

角色

Two category roles: 
bug
(something is broken), 
enhancement
(new feature or improvement).
Five state roles:
  • needs-triage
    — maintainer must evaluate
  • needs-info
    — waiting on reporter
  • ready-for-agent
    — fully specified, an AFK agent can take it
  • ready-for-human
    — needs a human
  • wontfix
    — will not be actioned
Every triaged issue carries exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything.
These are canonical roles. The actual label strings come from 
docs/agents/issue-tracker.md
(mapped by 
bootstrap
onto whatever the repo already uses). Don't apply the defaults verbatim if the repo renamed a role.
两类分类角色：
bug
（功能故障）、
enhancement
（新功能或改进）。
五类状态角色：
  • needs-triage
    — 需维护人员评估
  • needs-info
    — 等待反馈者回复
  • ready-for-agent
    — 已完全明确，离线Agent可接手处理
  • ready-for-human
    — 需人工处理
  • wontfix
    — 不会采取行动
每个完成分流的问题需恰好带有一个分类角色和一个状态角色。若状态角色存在冲突，请先标记并询问维护人员后再进行操作。
这些是标准角色。实际标签字符串来自
docs/agents/issue-tracker.md
（通过
bootstrap
映射到仓库已使用的标签）。若仓库重命名了角色，请不要直接使用默认标签。

State transitions

状态转换

An unlabeled issue → 
needs-triage
→ one of 
needs-info
, 
ready-for-agent
, 
ready-for-human
, 
wontfix
. 
needs-info
returns to 
needs-triage
once the reporter replies. The maintainer can override at any time — flag unusual transitions and ask before proceeding.
未标记的问题 → 
needs-triage
→ 转换为
needs-info
、
ready-for-agent
、
ready-for-human
、
wontfix
中的一种。当反馈者回复后，
needs-info
状态将转回
needs-triage
。维护人员可随时覆盖操作——若遇到异常转换，请先标记并询问后再继续。

Invocation

调用方式

The maintainer describes what they want in natural language ("show me anything that needs my input", "triage #42", "is this ready for an agent?"). Interpret and act.
维护人员用自然语言描述需求（如“展示所有需要我介入的内容”、“分流#42号问题”、“这个问题是否已准备好交给Agent处理？”）。需解读并执行相应操作。

Agent-ready briefs

Agent就绪简要说明

When moving an issue to 
ready-for-agent
, attach a brief an AFK agent can act on cold: the goal in the domain's vocabulary, the seams to test at, the files likely in scope, and the acceptance criteria. A brief that assumes conversation context is not ready.
当将问题转为
ready-for-agent
状态时，需附上一份可供离线Agent直接处理的简要说明：用领域术语描述目标、需测试的环节、可能涉及的文件以及验收标准。依赖对话上下文的简要说明不符合就绪要求。

Boundaries

边界范围

Categorises and transitions issues; writes briefs. Does not implement.
仅负责问题的分类与状态转换、撰写简要说明，不负责功能实现。