[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71Q7BSCMWRNQAPSK2GZEBFG":3,"skill-same:01M71Q7BSCMWRNQAPSK2GZEBFG":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":56},"01M71Q7BSCMWRNQAPSK2GZEBFG","triage",null,"让 issues 和 external PRs 通过一组 triage roles 状态机，分类、验证、必要时 grilling，并写出 agent-ready briefs。","vinvcn\u002Fmattpocock-skills-zh-CN","vinvcn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F120928190?v=4","01M71Q60C4V98DEXHGN2VXFSZB","01M71Q60D6PRAJHKQRY33ZNE59",5797,"MIT","https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftriage\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,23,24,25,26,27,28,29],"roles","ready","issues","prs","true","briefs","grilling","2026-11-10 13:02:02",false,"---\nname: triage\ndescription: 让 issues 和 external PRs 通过一组 triage roles 状态机，分类、验证、必要时 grilling，并写出 agent-ready briefs。\ndisable-model-invocation: true\n---\n\n# Triage\n\n通过一组小型 triage roles state machine，在项目 issue tracker 中移动 issues。\n\n如果这个 repo 把 external pull requests 当作 request surface（见 issue-tracker 配置），triage 也覆盖它们：**PR 是带附加代码的 issue**，相同的 roles、相同的 states、相同的 machine，只有下面标记为 “for a PR” 的几处差异。按 tracker 配置把裸 `#42` 解析为 issue 或 PR。\n\nTriage 期间发布到 issue tracker 的每条 comment 或 issue **必须**以此 disclaimer 开头：\n\n```\n> *This was generated by AI during triage.*\n```\n\n## 参考文档\n\n- [AGENT-BRIEF.md](AGENT-BRIEF.md)：如何写持久可用的 agent briefs\n- [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)：`.out-of-scope\u002F` knowledge base 如何工作\n\n## Roles\n\n两个 **category** roles：\n\n- `bug`：某个东西坏了\n- `enhancement`：新功能或改进\n\n五个 **state** roles：\n\n- `needs-triage`：maintainer 需要评估\n- `needs-info`：等待 reporter 提供更多信息\n- `ready-for-agent`：已完整说明，准备给 AFK agent 接手\n- `ready-for-human`：需要人工实现\n- `wontfix`：不会处理\n\n对 PR 而言，相同的 states 对照附加代码来解读：`ready-for-agent` 表示已附加 brief、agent 应对 diff 采取下一步；`ready-for-human` 表示已准备好由人类 merge。\n\n每个已 triage 的 issue 应该刚好携带一个 category role 和一个 state role。如果 state roles 冲突，标记出来并先询问 maintainer，再做其他事。\n\n这些是 canonical role names；issue tracker 中实际使用的 label strings 可能不同。映射应该已经提供给你；如果没有，请让用户运行 `\u002Fsetup-matt-pocock-skills`。\n\nState transitions：未标记的 issue 通常先进入 `needs-triage`；之后移动到 `needs-info`、`ready-for-agent`、`ready-for-human` 或 `wontfix`。`needs-info` 在 reporter 回复后回到 `needs-triage`。Maintainer 可以随时 override；对看起来异常的 transitions 标记并在继续前询问。\n\n## 调用\n\nMaintainer 调用 `\u002Ftriage`，并用自然语言描述想要什么。解释请求并行动。示例：\n\n- \"Show me anything that needs my attention\"\n- \"Let's look at #42\"（issue 或 PR）\n- \"Move #42 to ready-for-agent\"\n- \"What's ready for agents to pick up?\"\n\n## 展示需要关注的内容\n\n查询 issue tracker，并按最旧优先展示三个 buckets：\n\n1. **Unlabeled**：从未 triaged。\n2. **`needs-triage`**：evaluation in progress。\n3. **`needs-info` with reporter activity since the last triage notes**：需要重新评估。\n\n当 PRs 在范围内时，把 external PRs 纳入这些 buckets，并为每行标注 `[PR]` 或 `[issue]`。Discovery 只浮现 *external* PRs（tracker 配置定义了谁算 external），collaborator 正在进行的 PR 不是 triage 工作。这个过滤仅用于 discovery；被明确点名的 PR 无论作者是谁都会被 triage。\n\n显示每个 bucket 的数量，以及每个 issue 的一行摘要。让 maintainer 选择。\n\n## 对具体的 issue 或 PR 做 triage\n\n1. **Gather context.** 读取完整 issue 或 PR（body、comments、labels、author、dates；对 PR 还包括 diff）。解析任何之前的 triage notes，避免重新询问已解决的问题。使用项目 domain glossary 探索 codebase，并遵守相关 ADRs。对照 codebase 运行两项检查：(a) **redundancy**：按 domain concept（而不仅是请求的措辞）搜索所请求 behavior 的现有实现，并报告你查找过的地方。如果找到，那就是一个已实现的 `wontfix`（step 5）。(b) **prior rejection**：读取 `.out-of-scope\u002F*.md`，并浮现任何与此请求相似的既往拒绝。\n\n2. **Recommend.** 告诉 maintainer 你的 category 和 state 推荐及理由，并给出与请求相关的简短 codebase summary（包括它是否已经实现）。等待指示。\n\n3. **Verify the claim.** 在任何 grilling 前，检查该 claim 是否成立。对 bug，从 reporter 的步骤复现。对 PR，确认 diff 做到了它所声称的：checkout 它，运行相关 tests 或 commands。报告发生了什么：已确认（附 code path）、失败，或细节不足（强烈的 `needs-info` 信号）。已确认的验证会让 agent brief 更有力。\n\n4. **Grill（如果需要）.** 如果请求需要进一步充实，调用两次 Skill 工具，分别指定 `grilling` 和 `domain-modeling`，一轮一轮地把它 grill 成形，在 decisions 落定时打磨 domain terms 并内联更新 `GLOSSARY.md`\u002FADRs。\n\n5. **Apply the outcome:**\n   - `ready-for-agent`：发布 agent brief comment（[AGENT-BRIEF.md](AGENT-BRIEF.md)）。\n   - `ready-for-human`：使用与 agent brief 相同的结构，但说明为什么不能委托（judgment calls、external access、design decisions、manual testing）。\n   - `needs-info`：发布 triage notes（见下方 template）。\n   - `wontfix`：close，comment 取决于*原因*：\n     - **Already implemented**：change 已存在于 codebase 中。指向它所在的位置；**不要**写入 `.out-of-scope\u002F`（那个 KB 是为*被拒绝*的请求准备的，不是为已构建的）。\n     - **Rejected（bug）**：礼貌解释，然后 close。\n     - **Rejected（enhancement）**：写入 `.out-of-scope\u002F`，从 comment 链接到它，然后 close（[OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)）。\n   - `needs-triage`：应用 role。如果有部分进展，可选择 comment。\n\n## 快速状态覆盖\n\n如果 maintainer 说 “move #42 to ready-for-agent”，相信他们并直接应用 role。确认你即将做什么（role changes、comment、close），然后执行。跳过 grilling。如果在没有 grilling session 的情况下移动到 `ready-for-agent`，询问他们是否想写 agent brief。\n\n## Needs-info 模板\n\n```markdown\n## Triage Notes\n\n**What we've established so far:**\n\n- point 1\n- point 2\n\n**What we still need from you (@reporter):**\n\n- question 1\n- question 2\n```\n\n把 grilling 期间已经解决的所有内容都捕获到 “established so far” 下，避免工作丢失。问题必须具体且可执行，而不是 “please provide more info”。\n\n## 恢复上一次 session\n\n如果 issue 或 PR 上已有 triage notes，读取它们，检查 reporter 是否回答了任何 outstanding questions，并在继续前展示更新后的情况。不要重复询问已解决的问题。\n","# Triage\n\n通过一组小型 triage roles state machine，在项目 issue tracker 中移动 issues。\n\n如果这个 repo 把 external pull requests 当作 request surface（见 issue-tracker 配置），triage 也覆盖它们：**PR 是带附加代码的 issue**，相同的 roles、相同的 states、相同的 machine，只有下面标记为 “for a PR” 的几处差异。按 tracker 配置把裸 `#42` 解析为 issue 或 PR。\n\nTriage 期间发布到 issue tracker 的每条 comment 或 issue **必须**以此 disclaimer 开头：\n\n```\n> *This was generated by AI during triage.*\n```\n\n## 参考文档\n\n- [AGENT-BRIEF.md](AGENT-BRIEF.md)：如何写持久可用的 agent briefs\n- [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)：`.out-of-scope\u002F` knowledge base 如何工作\n\n## Roles\n\n两个 **category** roles：\n\n- `bug`：某个东西坏了\n- `enhancement`：新功能或改进\n\n五个 **state** roles：\n\n- `needs-triage`：maintainer 需要评估\n- `needs-info`：等待 reporter 提供更多信息\n- `ready-for-agent`：已完整说明，准备给 AFK agent 接手\n- `ready-for-human`：需要人工实现\n- `wontfix`：不会处理\n\n对 PR 而言，相同的 states 对照附加代码来解读：`ready-for-agent` 表示已附加 brief、agent 应对 diff 采取下一步；`ready-for-human` 表示已准备好由人类 merge。\n\n每个已 triage 的 issue 应该刚好携带一个 category role 和一个 state role。如果 state roles 冲突，标记出来并先询问 maintainer，再做其他事。\n\n这些是 canonical role names；issue tracker 中实际使用的 label strings 可能不同。映射应该已经提供给你；如果没有，请让用户运行 `\u002Fsetup-matt-pocock-skills`。\n\nState transitions：未标记的 issue 通常先进入 `needs-triage`；之后移动到 `needs-info`、`ready-for-agent`、`ready-for-human` 或 `wontfix`。`needs-info` 在 reporter 回复后回到 `needs-triage`。Maintainer 可以随时 override；对看起来异常的 transitions 标记并在继续前询问。\n\n## 调用\n\nMaintainer 调用 `\u002Ftriage`，并用自然语言描述想要什么。解释请求并行动。示例：\n\n- \"Show me anything that needs my attention\"\n- \"Let's look at #42\"（issue 或 PR）\n- \"Move #42 to ready-for-agent\"\n- \"What's ready for agents to pick up?\"\n\n## 展示需要关注的内容\n\n查询 issue tracker，并按最旧优先展示三个 buckets：\n\n1. **Unlabeled**：从未 triaged。\n2. **`needs-triage`**：evaluation in progress。\n3. **`needs-info` with reporter activity since the last triage notes**：需要重新评估。\n\n当 PRs 在范围内时，把 external PRs 纳入这些 buckets，并为每行标注 `[PR]` 或 `[issue]`。Discovery 只浮现 *external* PRs（tracker 配置定义了谁算 external），collaborator 正在进行的 PR 不是 triage 工作。这个过滤仅用于 discovery；被明确点名的 PR 无论作者是谁都会被 triage。\n\n显示每个 bucket 的数量，以及每个 issue 的一行摘要。让 maintainer 选择。\n\n## 对具体的 issue 或 PR 做 triage\n\n1. **Gather context.** 读取完整 issue 或 PR（body、comments、labels、author、dates；对 PR 还包括 diff）。解析任何之前的 triage notes，避免重新询问已解决的问题。使用项目 domain glossary 探索 codebase，并遵守相关 ADRs。对照 codebase 运行两项检查：(a) **redundancy**：按 domain concept（而不仅是请求的措辞）搜索所请求 behavior 的现有实现，并报告你查找过的地方。如果找到，那就是一个已实现的 `wontfix`（step 5）。(b) **prior rejection**：读取 `.out-of-scope\u002F*.md`，并浮现任何与此请求相似的既往拒绝。\n\n2. **Recommend.** 告诉 maintainer 你的 category 和 state 推荐及理由，并给出与请求相关的简短 codebase summary（包括它是否已经实现）。等待指示。\n\n3. **Verify the claim.** 在任何 grilling 前，检查该 claim 是否成立。对 bug，从 reporter 的步骤复现。对 PR，确认 diff 做到了它所声称的：checkout 它，运行相关 tests 或 commands。报告发生了什么：已确认（附 code path）、失败，或细节不足（强烈的 `needs-info` 信号）。已确认的验证会让 agent brief 更有力。\n\n4. **Grill（如果需要）.** 如果请求需要进一步充实，调用两次 Skill 工具，分别指定 `grilling` 和 `domain-modeling`，一轮一轮地把它 grill 成形，在 decisions 落定时打磨 domain terms 并内联更新 `GLOSSARY.md`\u002FADRs。\n\n5. **Apply the outcome:**\n   - `ready-for-agent`：发布 agent brief comment（[AGENT-BRIEF.md](AGENT-BRIEF.md)）。\n   - `ready-for-human`：使用与 agent brief 相同的结构，但说明为什么不能委托（judgment calls、external access、design decisions、manual testing）。\n   - `needs-info`：发布 triage notes（见下方 template）。\n   - `wontfix`：close，comment 取决于*原因*：\n     - **Already implemented**：change 已存在于 codebase 中。指向它所在的位置；**不要**写入 `.out-of-scope\u002F`（那个 KB 是为*被拒绝*的请求准备的，不是为已构建的）。\n     - **Rejected（bug）**：礼貌解释，然后 close。\n     - **Rejected（enhancement）**：写入 `.out-of-scope\u002F`，从 comment 链接到它，然后 close（[OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)）。\n   - `needs-triage`：应用 role。如果有部分进展，可选择 comment。\n\n## 快速状态覆盖\n\n如果 maintainer 说 “move #42 to ready-for-agent”，相信他们并直接应用 role。确认你即将做什么（role changes、comment、close），然后执行。跳过 grilling。如果在没有 grilling session 的情况下移动到 `ready-for-agent`，询问他们是否想写 agent brief。\n\n## Needs-info 模板\n\n```markdown\n## Triage Notes\n\n**What we've established so far:**\n\n- point 1\n- point 2\n\n**What we still need from you (@reporter):**\n\n- question 1\n- question 2\n```\n\n把 grilling 期间已经解决的所有内容都捕获到 “established so far” 下，避免工作丢失。问题必须具体且可执行，而不是 “please provide more info”。\n\n## 恢复上一次 session\n\n如果 issue 或 PR 上已有 triage notes，读取它们，检查 reporter 是否回答了任何 outstanding questions，并在继续前展示更新后的情况。不要重复询问已解决的问题。\n",{"name":5,"description":7,"disable-model-invocation":35},true,"main","c5c5e87cc1df26aeb7dba345ad9f846434d2b3d4","skills\u002Fengineering\u002Ftriage",450,"https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN","https:\u002F\u002Fskills.sh\u002Fvinvcn\u002Fmattpocock-skills-zh-CN","https:\u002F\u002Fgithub.com\u002Fvinvcn","2026-11-10 17:40:42",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":35},[46,49,52],{"tool":47,"command":48},"npx","npx skills add vinvcn\u002Fmattpocock-skills-zh-CN --skill triage",{"tool":50,"command":51},"bunx","bunx skills add vinvcn\u002Fmattpocock-skills-zh-CN --skill triage",{"tool":53,"command":54},"pnpm","pnpm dlx skills add vinvcn\u002Fmattpocock-skills-zh-CN --skill triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftriage\u002FSKILL.md",[57,63,67],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"AGENT-BRIEF.md","REFERENCE","参考文档",7786,"https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftriage\u002FAGENT-BRIEF.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"agents\u002Fopenai.yaml",133,"https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftriage\u002Fagents\u002Fopenai.yaml",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"OUT-OF-SCOPE.md",4460,"https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Ftriage\u002FOUT-OF-SCOPE.md",[72,92,101,111,121,130],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":87,"publishedAt":30},"01M71Q8F3M8YFP6WYVYQP61KBT","writing-for-agents","为 agent 编写文档。适用于创建或编辑 skills，或修改 AGENTS.md 或 CLAUDE.md 时。","https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-for-agents\u002FSKILL.md",[78,81,82],{"categoryNo":79,"categoryName":80,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[88,89,90,91],"for","writing for agents","writing","文档",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":30},"01M71Q8DHRPYE6R648CQ7NAHYN","wait-what","停一下：刚才那条消息没有说清楚，重新表述一遍。","https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwait-what\u002FSKILL.md",[],[99,100,27],"wait","wait what",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":30},"01M71Q8C8CBSRJRP8Y0JRZ7RJ7","to-questionnaire","把你无法完整回答的 decision 转成一份交给他人填写的 questionnaire。","https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fto-questionnaire\u002FSKILL.md",[],[108,109,110,27],"questionnaire","to questionnaire","decision",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":120,"publishedAt":30},"01M71Q8ASS9A6P84PSC02YFKHB","teach","在这个工作区中教用户一个新技能或概念。","https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fteach\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000039","教师与教育",[113,27],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":30},"01M71Q89C2C2QRR3J3H64ZKH0P","handoff","把当前对话压缩成交接文档，让另一个代理接手。","https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[123,27,128,129,91],"对话","压缩",{"skillNo":131,"name":29,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":30},"01M71Q883CXWF0BGDQC3Y8TJZ2","围绕计划、decision 或 idea 持续追问用户。适用于用户想对自己的思路做压力测试，或使用任何 “grill” 触发措辞时。","https:\u002F\u002Fgithub.com\u002Fvinvcn\u002Fmattpocock-skills-zh-CN\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fgrilling\u002FSKILL.md",[],[29,136,137,110,138],"idea","grill","testing"]