agentleFS
Sign inStart free
Fei2411Fei2411/DeepSeek-Bot/.agents/skills/issue-triage/SKILL.md

issue-triage

Skill6.3k starsChanged 21 days agoApache-2.0View on GitHub

给 DS Bot 仓库的 Issue 和 PR 分诊：打类型、优先级、领域标签，判断该关闭、追问、转讨论还是留着做，并把结论写回 GitHub。触发词：分诊、整理 Issue、打标签、打优先级、这个该不该关、追问报告人、needs-info 到期。

63 other projects use a version of this.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 13 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Fei2411/DeepSeek-Bot repository that our weekly crawl found: only 13 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Fei2411/DeepSeek-Bot

The biggest 5 of 13 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 13

Talked about on GitHub and Bluesky (13 times).

On GitHub · 12

7 more on GitHub

On Bluesky · 1

Used with

Projects with it also use meeting-notes-and-actions, pr-review-ci-fix and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ComposioHQSkill

    meeting-notes-and-actions

    Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.

    Also in 4 projects that use this

  • ComposioHQSkill

    pr-review-ci-fix

    Automated PR review and CI auto-fix for GitHub and GitLab using the Composio CLI. Pulls diffs, fetches failing job logs, posts review comments, and loops fix commits until checks go green.

    Also in 4 projects that use this

  • FlorianBruniauxSkill

    tdd-rust

    Also in 3 projects that use this

  • GitHubSkill

    phoenix-cli

    Debug LLM applications using the Phoenix CLI. Fetch traces, analyze errors, structure trace review with open coding and axial coding, inspect datasets, review experiments, query annotation configs, and use the GraphQL API. Use whenever the user is analyzing traces or spans, investigating LLM/agent failures, deciding what to do after instrumenting an app, building failure taxonomies, choosing what evals to write, or asking "what's going wrong", "what kinds of mistakes", or "where do I focus" — even without naming a technique.

    Also in 3 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • +7 more from ComposioHQ

The file

Create a free account to mount
Files
SKILL.md

Issue 分诊

目标：每个 Open Issue 都有一个类型、一个优先级，需要时有一个领域；每个关闭的 Issue 都有证据。

标签的含义和流程以 CONTRIBUTING.zh.md 为准，本文只写怎么做。

边界：只动 Issue、PR 的标签、评论和关闭状态。不改代码，不改 Issue 正文，不合并 PR。带 maintainer 的条目只分诊、不下结论。

1. 取快照

在仓库根目录运行（只读，不写 GitHub）：

node .agents/skills/issue-triage/scripts/snapshot.mjs --out /tmp/triage

先读 digest.md 再判断，不要只看标题。digest 把每个 Issue 列成：标签、天数、评论数、正文和别人评论的摘要、dev/main 上引用它的提交、引用它的 Open PR。最上面是待处理：

  • 没有类型或没有优先级的
  • 有两个优先级的
  • needs-info 超过 14 天、报告人没再回复的

动手之前读一遍 references/gh-gotchas.md。

2. 分类

每条落三个坐标：

坐标取值怎么判
类型bug · enhancement · documentation行为和设计不一致才是 bug。设计本来就这样、用户想要别的，是 enhancement。拿不准时先读 docs/vision.zh.md 和 docs/plans/
优先级P0–P3P0 崩溃、丢数据、完全不能用 · P1 影响日常使用、刚引入的回归 · P2 普通 bug 或功能 · P3 建议、窄场景
领域area/* 之一按改动会落在哪个目录判。跨好几个领域或不属于任何领域，就不挂

规则：

  • 已有的优先级默认保留。那是之前的判断，不是噪声。觉得该改，在评论里说理由。
  • 一个 Issue 只有一个 P 标签。--add-label 不会去掉旧的，改优先级要同时 --remove-label。
  • PR 不打类型和领域。

3. 判动作

按证据归组。证据不够就留着做，不要猜着关。

组判据动作
已修，未发版dev 上有提交或已合并的 PR 修了它不关。评论写明 PR 号，等发版时 Release PR 的 Fixes #N 自动关
已修，已发版main 上有修复，CHANGELOG 有记录，或能指出守住它的测试completed 关，评论写具体的 PR、提交或测试名
重复和另一个 Issue 是同一个原因加 duplicate，链接那一个，not planned 关
上游原因在 DSH 或别的插件加 upstream，链接该去的地方。我们这边无事可做时 not planned 关
提问怎么装、怎么用在网页上 Convert to discussion，转到 Q&A（CLI 做不了，见 gotchas）
缺信息现象定位不了，没有版本、日志或复现步骤加 needs-info，追问一次（模板见下）
needs-info 到期追问后 14 天没有新信息not planned 关，评论写「没有收到补充信息，补充后会重新打开」
有 PR 在做有 Open PR 引用它不动
需要方向涉及产品方向、已定设计、协作规则、发版、架构加 maintainer，等维护者
留着做其余打好标签就行。小而清楚的可以加 good first issue

4. 写评论和关闭

  • 用 Issue 自己的语言：正文是中文就用中文，否则用英文。
  • 关闭的评论必须是「为什么可以关」的证据：PR 号、提交号、文件和测试名、重复的 Issue 号、报告人自己的更正。
  • 一条命令完成关闭和评论：gh issue close <n> --reason "completed" --comment-file <file> 或 --reason "not planned"。
  • 中文评论先写进 UTF-8 文件，再用 --body-file 或 --comment-file 发。

追问模板（按情况删改，写清楚缺什么）：

感谢反馈。为了找到原因，请补充：
1. DS Bot 和 DSH 的版本。
2. ……（具体缺的东西）
3. ……

14 天内没有新信息，我们会先关闭这个 Issue；补充后我们会重新打开。

5. 回读自查

写回之后再拉一次，确认：

gh issue list --state open --limit 300 --json number,labels --jq '.[] | select([.labels[].name | select(test("^P[0-3]$"))] | length != 1) | .number'
gh issue list --state open --limit 300 --json number,labels --jq '.[] | select([.labels[].name | select(. == "bug" or . == "enhancement" or . == "documentation")] | length == 0) | .number'

两条都没有输出才算完成。

6. 汇报

向提出请求的人汇报一张表：编号、标题、打了什么标签、动作、证据。关闭和追问在执行前先给对方看；对方确认后再发。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free