Back to Details

triage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Herdr Issue Triage

Herdr 问题分类管理

Use this skill only inside the herdr repository.
When the user says 
triage
, inspect open GitHub issues for 
herdrdev/herdr
and return a concise Markdown table. Prefer GitHub MCP tools when available. If they are unavailable, use 
gh issue list
/ 
gh issue view
only when authenticated access is already configured.
Use this table shape:
LightRecommendationIssueAgeReactionsWhy
🔴fix now#12318d5user-visible regression
🟡queue#12442d2useful but not blocking
🔵defer#1257d0cosmetic polish
Keep issue numbers as Markdown links. Use days since issue creation for 
Age
. Use total reactions for 
Reactions
; include a compact breakdown only when it changes interpretation, such as 
7 (5 👍, 2 👀)
.
Classify with these lights:
  • 🔴 
    fix now
    : reproducible bug, crash, data loss, blocked workflow, release risk, or high-confidence user-visible regression.
  • 🟡 
    queue
    : useful feature, important quality issue, repeated user signal, stale issue that still looks valid, or behavior worth scheduling.
  • 🔵 
    defer
    : cosmetic polish, low-signal idea, unclear report, docs-only nit, or issue that likely needs more evidence before implementation.
Recommendations should be short imperative phrases: 
fix now
, 
queue
, 
defer
, 
needs repro
, 
close?
, or 
needs owner decision
.
Write one sentence before the table only if needed to state scope, such as how many open issues were inspected. After the table, add at most one short note for uncertainty or follow-up. Do not produce a long narrative unless the user asks for depth.
仅在herdr仓库内使用此技能。
当用户输入
triage
时，检查
herdrdev/herdr
的GitHub开放问题，并返回一个简洁的Markdown表格。若有可用的GitHub MCP工具，请优先使用；若不可用，仅在已配置认证访问的情况下使用
gh issue list
/ 
gh issue view
。
使用如下表格格式：
标识建议问题时长互动数原因
🔴立即修复#12318d5用户可见的功能退化
🟡排入队列#12442d2有用但不阻塞流程
🔵延后处理#1257d0外观优化
将问题编号保留为Markdown链接。
时长
使用问题创建后的天数。
互动数
使用总互动次数；仅当互动细分会影响判断时，才添加紧凑的细分说明，例如
7 (5 👍, 2 👀)
。
使用以下标识进行分类：
  • 🔴 
    立即修复
    ：可复现的bug、崩溃、数据丢失、流程阻塞、发布风险，或高可信度的用户可见功能退化。
  • 🟡 
    排入队列
    ：实用功能、重要质量问题、重复用户反馈、仍有效的陈旧问题，或值得排期处理的行为优化。
  • 🔵 
    延后处理
    ：外观优化、低价值想法、表述模糊的报告、仅文档细节问题，或在实施前可能需要更多证据的问题。
建议应使用简短的祈使短语：
立即修复
、
排入队列
、
延后处理
、
需要复现
、
是否关闭？
，或
需要负责人决策
。
仅在需要说明范围时（例如检查了多少个开放问题），在表格前写一句话。表格后最多添加一条关于不确定性或后续跟进的简短说明。除非用户要求详细内容，否则不要生成冗长的叙述。