An issue-triage workflow for sorting bug reports and feature requests, including pull requests. Triage means reviewing incoming work, asking for missing information, and giving it a clear status and handoff brief.

Use it to classify issues, request missing details, review external pull requests, assign workflow states, and write briefs that an agent can act on.

It prevents incoming work from sitting unclassified or being handed to an agent without enough context. It also provides consistent states for work that needs information, an agent, a human, or no action.

triage-zh — Skill for Claude Code by gongyijie85

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add gongyijie85/mattpocock-skills-dsh-zh --skill triage-zh

Clone the repo

git clone --depth 1 https://github.com/gongyijie85/mattpocock-skills-dsh-zh

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gongyijie85/mattpocock-skills-dsh-zh/triage-zh/github.svg)](https://agentmods.dev/skills/gongyijie85/mattpocock-skills-dsh-zh/triage-zh)

Your own site

<a href="https://agentmods.dev/skills/gongyijie85/mattpocock-skills-dsh-zh/triage-zh"><img src="https://agentmods.dev/badge/skills/gongyijie85/mattpocock-skills-dsh-zh/triage-zh/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gongyijie85/mattpocock-skills-dsh-zh/triage-zh"><img src="https://agentmods.dev/badge/skills/gongyijie85/mattpocock-skills-dsh-zh/triage-zh.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,809 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 86% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00047	$0.01809
Opus 5	$0.00023	$0.00905
Sonnet 5	$0.00009	$0.00362
Haiku 4.5	$0.00005	$0.00181

Measured yesterday against content hash 7d67bf984f20, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

triage-zh scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

86% identical to triage — 94 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/triage-zh/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

分流(Triage)

让项目 issue tracker 上的 issues 沿着小型 triage 角色状态机流转。

如果本仓库把外部 pull request 也当作请求入口(参见 issue-tracker 配置),triage 同样覆盖它们:PR 就是附带了代码的 issue——同样的角色、同样的状态、同样的状态机,只是下面标注了几处 "for a PR" 的差异。根据 tracker 配置把裸 #42 解析为 issue 或 PR。

triage 期间发布到 issue tracker 的每条评论或 issue 必须以这段免责声明开头:

> *This was generated by AI during triage.*

参考文档

AGENT-BRIEF.md — 如何撰写持久的 agent brief
OUT-OF-SCOPE.md — .out-of-scope/ 知识库如何运作

角色

两个 分类(category) 角色:

bug — 某样东西坏了
enhancement — 新功能或改进

五个 状态(state) 角色:

needs-triage — 维护者需要评估
needs-info — 等待报告者提供更多信息
ready-for-agent — 已完整说明,可供 AFK agent 接手
ready-for-human — 需要人类实现
wontfix — 不会被处理

对于 PR,同样的状态要对照其附带的代码来解读:ready-for-agent 意味着已附上 brief,agent 应对 diff 采取下一步行动;ready-for-human 意味着已准备好由人类合并。

每个经过 triage 的 issue 应恰好携带一个 category 角色和一个 state 角色。如果 state 角色冲突,先标记出来并向维护者询问,再做任何其它事情。

这些是规范角色名——issue tracker 中实际使用的标签字符串可能不同。映射关系应当已经提供给你。如果没有,告诉用户运行 setup-matt-pocock-skills。

状态转换:未打标签的 issue 通常先进入 needs-triage;从那里它移动到 needs-info、ready-for-agent、ready-for-human 或 wontfix。报告者回复后,needs-info 返回 needs-triage。维护者可以随时覆盖——标记看起来不寻常的转换,并在继续之前询问。

调用

维护者调用 triage 并用自然语言描述需求。解读请求并执行。示例:

"把需要我关注的东西都展示给我"
"我们看看 #42"(issue 或 PR)
"把 #42 移到 ready-for-agent"
"有哪些是 agent 可以认领的?"

展示需要关注的内容

查询 issue tracker,按最旧在前呈现三个桶:

未打标签(Unlabeled) — 从未被 triage 过。
needs-triage — 评估进行中。
needs-info 且自上次 triage 笔记以来报告者有新活动 — 需要重新评估。

当 PR 在范围内时,把外部 PR 纳入这些桶,并为每行标注 [PR] 或 [issue]。发现(discovery)只暴露_外部_PR(tracker 配置定义谁算外部)——协作者进行中的 PR 不是 triage 工作。这个过滤只作用于发现阶段;明确点名的 PR 无论作者是谁都始终会被 triage。

显示每个条目的计数和一行摘要。让维护者挑选。

Triage 一个具体的 issue 或 PR

收集上下文。 通读完整的 issue 或 PR(正文、评论、标签、作者、日期;PR 还要看 diff)。解析任何先前的 triage 笔记,避免重复询问已解决的问题。使用项目的领域词汇表探索代码库,尊重所触及区域的 ADR。对照代码库执行两项检查:(a) 冗余(redundancy)——按领域概念(而不只是请求的措辞)搜索请求的行为是否已有实现,并报告你查找过哪里。如果找到了,它就是一个已实现的 wontfix(第 5 步)。(b) 先前拒绝(prior rejection)——阅读 .out-of-scope/*.md,指出任何与本次请求相似的条目。

Read the full file on GitHub · 113 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 113 lines · 47 tokens per session scan A 7d67bf984f20

Subscribe to this mod's changes

triage-zh is a skill published in the GitHub repository gongyijie85/mattpocock-skills-dsh-zh (5 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,809 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to triage, differing in 94 lines, and is treated as a copy.

Project management agent-skills chinese deepseek-harness dsh dsh-plugin mattpocock

manage-taskboard

Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…

shengsheng90/DSH-taskboard · 88 tokens

dev-team

Simulate a collaborative dev team session where multiple role-based personas (PM, Architect, Developer, QA) respond to the same problem together in one session. Use when designing a feature, reviewing a proposal, or onboarding a new initiative and you want multi-role perspective without switching agents manually.

gongyijie85/dsh-ecc · 60 tokens

triage-zh