gh-issue-triage

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Issue Triage

问题分流处理

Rules and workflows for categorizing, labeling, and prioritizing GitHub issues.

用于GitHub Issues分类、打标签及优先级排序的规则与工作流。

Quick Reference

快速参考

Label Type	Purpose	Mutually Exclusive?
Type	What kind of issue	Yes
Priority	How urgent	Yes
Status	Current state	Yes
Area	Which component	No

标签类型	用途	是否互斥？
Type	问题类型	是
Priority	紧急程度	是
Status	当前状态	是
Area	涉及组件	否

Label Taxonomy

标签分类体系

Type Labels (mutually exclusive)

类型标签（互斥）

Label	Description	Color
`bug`	Something is broken	`#d73a4a` (red)
`feature`	New functionality	`#a2eeef` (cyan)
`enhancement`	Improvement to existing feature	`#84b6eb` (blue)
`docs`	Documentation only	`#0075ca` (dark blue)
`chore`	Maintenance, deps, infra	`#fef2c0` (yellow)

标签	描述	颜色
`bug`	功能出现故障	`#d73a4a` （红色）
`feature`	新增功能	`#a2eeef` （青色）
`enhancement`	现有功能优化	`#84b6eb` （蓝色）
`docs`	仅涉及文档	`#0075ca` （深蓝色）
`chore`	维护工作、依赖更新、基础设施调整	`#fef2c0` （黄色）

Priority Labels (mutually exclusive)

优先级标签（互斥）

Label	Description	Response
`priority: critical`	Drop everything, fix now	Immediate
`priority: high`	Next up after current work	This sprint
`priority: medium`	Normal backlog	Scheduled
`priority: low`	Nice to have, someday	Backlog

标签	描述	响应要求
`priority: critical`	暂停所有工作，立即修复	立即处理
`priority: high`	当前工作完成后优先处理	本迭代完成
`priority: medium`	常规待办项	排期处理
`priority: low`	锦上添花的需求，后续再处理	放入待办积压

Status Labels (mutually exclusive)

状态标签（互斥）

Label	Description
`needs-triage`	New, not yet categorized
`needs-info`	Waiting for reporter clarification
`accepted`	Triaged and in backlog
`in-progress`	Someone is working on it
`blocked`	Can't proceed, waiting on something

标签	描述
`needs-triage`	新创建，尚未分类
`needs-info`	等待反馈者补充信息
`accepted`	已完成分流，加入待办积压
`in-progress`	有人正在处理
`blocked`	无法推进，等待依赖项

Area Labels (project-specific, not exclusive)

领域标签（项目专属，不互斥）

Define based on your project structure:

```
area: api
```
```
area: cli
```
```
area: docs
```
```
area: ui
```
```
area: auth
```

根据项目结构定义：

```
area: api
```
```
area: cli
```
```
area: docs
```
```
area: ui
```
```
area: auth
```

Triage Workflow

分流处理工作流

Step 1: New Issues

步骤1：新创建的问题

Every new issue gets

needs-triage

label automatically (via GitHub Actions or manually).

所有新问题会自动添加

needs-triage

标签（通过GitHub Actions或手动添加）。

Step 2: Initial Review

步骤2：初步审核

Is this a duplicate?
  YES → Close with "Duplicate of #N", link original
  NO  → Continue

Is this spam/invalid?
  YES → Close without label
  NO  → Continue

Is the issue clear enough to act on?
  YES → Continue to Step 3
  NO  → Add `needs-info`, comment asking for clarification

是否为重复问题？
  是 → 关闭并标注“重复自#N”，链接原问题
  否 → 继续

是否为垃圾信息/无效问题？
  是 → 直接关闭，不添加标签
  否 → 继续

问题描述是否清晰到可以处理？
  是 → 进入步骤3
  否 → 添加`needs-info`标签，评论要求补充说明

Step 3: Categorization

步骤3：分类

Apply type label:
  - Broken functionality → `bug`
  - New capability → `feature`
  - Improve existing → `enhancement`
  - Documentation → `docs`
  - Maintenance → `chore`

Apply area label(s):
  - Based on affected component
  - Can have multiple areas

添加类型标签：
  - 功能故障 → `bug`
  - 新功能需求 → `feature`
  - 现有功能优化 → `enhancement`
  - 文档相关 → `docs`
  - 维护工作 → `chore`

添加领域标签：
  - 根据受影响的组件选择
  - 可添加多个领域标签

Step 4: Prioritization

步骤4：优先级设定

Apply priority:
  - Production down / security issue → `priority: critical`
  - Major impact, many users → `priority: high`
  - Normal request → `priority: medium`
  - Nice to have → `priority: low`

添加优先级标签：
  - 生产环境宕机/安全问题 → `priority: critical`
  - 影响范围大、涉及大量用户 → `priority: high`
  - 常规需求 → `priority: medium`
  - 锦上添花的需求 → `priority: low`

Step 5: Finalize

步骤5：最终确认

1. Remove `needs-triage`
2. Add `accepted`
3. Assign to milestone (if applicable)
4. Suggest assignee (if known)

1. 移除`needs-triage`标签
2. 添加`accepted`标签
3. 关联到里程碑（如有需要）
4. 建议处理人（如已知）

Priority Guidelines

优先级指南

Critical

紧急（Critical）

Production is down
Security vulnerability
Data loss occurring
Blocks all users

生产环境宕机
安全漏洞
正在发生数据丢失
阻塞所有用户使用

High

高优先级（High）

Major feature broken
Significant user impact
Blocks important workflow
Time-sensitive deadline

核心功能故障
严重影响用户使用
阻塞重要工作流
有时间限制的截止日期

Medium

中优先级（Medium）

Normal bug reports
Feature requests
Improvements
Most issues land here

常规bug反馈
功能需求
优化建议
大多数问题属于此类

Low

低优先级（Low）

Minor cosmetic issues
Edge case bugs
Nice-to-have features
"Someday" items

轻微界面问题
边缘场景bug
锦上添花的功能
“未来再做”的事项

Common Patterns

常见场景处理

Insufficient Information

信息不足

Issue: "It doesn't work"
Action:
1. Add `needs-info`
2. Comment: "Can you provide steps to reproduce and your environment?"
3. Wait for response

问题：“它用不了”
处理动作：
1. 添加`needs-info`标签
2. 评论：“能否提供复现步骤和你的环境信息？”
3. 等待回复

Duplicate Detection

重复问题检测

Issue: Similar to existing #123
Action:
1. Close issue
2. Comment: "Duplicate of #123"
3. Add any new context to #123

问题：与现有问题#123类似
处理动作：
1. 关闭当前问题
2. 评论：“重复自#123”
3. 将新补充的信息添加到#123中

Critical Security Issue

紧急安全问题

Issue: Security vulnerability
Action:
1. Add `priority: critical`, `bug`
2. Assign immediately
3. Consider private discussion

问题：存在安全漏洞
处理动作：
1. 添加`priority: critical`和`bug`标签
2. 立即分配处理人
3. 考虑使用私有讨论

Feature Without Acceptance Criteria

无验收标准的功能需求

Issue: "Add dark mode"
Action:
1. Add `feature`, `needs-info`
2. Comment: "Great idea! Can you describe acceptance criteria?"

问题：“添加暗色模式”
处理动作：
1. 添加`feature`和`needs-info`标签
2. 评论：“好主意！能否描述验收标准？”

Reference Files

参考文件

See

references/

for:

```
label-taxonomy.md
```
- Complete label reference with colors

查看

references/

目录下的文件：

```
label-taxonomy.md
```
- 包含颜色信息的完整标签参考文档

Integration with Other Components

与其他组件的集成

Typical Triage Workflow

典型分流处理工作流

Issue created using gh-issue-templates (gets
```
needs-triage
```
label)
Use gh-issue-triage (this skill) to determine type and priority
Apply labels using gh-wrangler agent
Track state changes using gh-issue-lifecycle

使用gh-issue-templates创建格式规范的问题（自动添加
```
needs-triage
```
标签）
使用gh-issue-triage（本技能）确定问题类型与优先级
使用gh-wrangler Agent添加标签
使用gh-issue-lifecycle跟踪状态变化

Label Setup

标签设置

Use

references/label-taxonomy.md

to:

Create labels with correct colors:
```
gh label create "bug" --color "d73a4a"
```
Maintain consistent taxonomy across repositories
Setup new repositories with standard labels

使用

references/label-taxonomy.md

来：

创建带有正确颜色的标签：
```
gh label create "bug" --color "d73a4a"
```
在所有仓库中保持一致的标签分类体系
为新仓库配置标准标签

Priority Assignment

优先级分配

Consult "Priority Guidelines" section in this skill:

Critical: Production down, security, data loss
High: Major features broken, significant impact
Medium: Normal bugs and features (most issues)
Low: Nice-to-have, cosmetic, edge cases

参考本技能中的“优先级指南”部分：

Critical：生产环境宕机、安全问题、数据丢失
High：核心功能故障、严重影响
Medium：常规bug与功能需求（大多数问题）
Low：锦上添花、界面美化、边缘场景