triage
仓库创建 2026年7月6日最近提交 22 天前SkillHot 收录 22 天前
▸ 精选理由
适合维持高质量的 issue 流程并为后续代理工作准备好上下文。
▸ 风险提示
需要对 issue/PR 有读写权限
这个 Skill 做什么
将 issues/PR 通过一套小状态机完成分类、验证与产出代理可执行简报。
把 issue 和外部 PR 拉进一个小状态机里完成分类、验证、必要时追问并输出给代理人可直接执行的简报。用于项目问题跟踪时把杂乱的报告变成可行动的任务清单,PR 在这里被当成带代码的 issue 一并处理。亮点是把 triage 流程标准化,既能判优先级也能生成后续处理所需的背景与结论。
▸ 展开 SKILL.md 英文原文
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
0
Stars
0
Forks
38
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/K3639284/skills/main/skills/engineering/triage/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/K3639284/skills/main/skills/engineering/triage/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# Triage Move issues on the project issue tracker through a small state machine of triage roles. If this repo treats external pull requests as a request surface (see the issue-tracker config), triage covers them too: **a PR is an issue with attached code** — same roles, same states, same machine, with a few deltas marked "for a PR" below. Resolve a bare `#42` to an issue or PR per the tracker config. Every comment or issue posted to the issue tracker during triage **must** start with this disclaimer: ``` > *This was generated by AI during triage.* ``` ## Reference docs - [AGENT-BRIEF.md](AGENT-BRIEF.md) — how to write durable agent briefs - [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md) — how the
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有