agentleFS
Sign inStart free
9Ashwin9Ashwin/let-it-go/skills/bonus/triage/SKILL.md

triage

Skill0 starsChanged 35 days agoMITView on GitHub

处理别人提的原始 issue 与 bug 报告：复现、定角色、补成 agent 可执行的卡片，信息不足时按模板要信息。Triggers: triage, 分诊, 处理 issue, 一堆 bug, 归类, 要信息, 清理 issue.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing-beats, setup-matt-pocock-skills 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.
  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 66 projects that use this

  • GoogleSkill

    setup-matt-pocock-skills

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

    Also in 167 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 68 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 63 projects that use this

  • +1 more from Lesani

The file

Create a free account to mount
Files
SKILL.md

triage — 把进来的原始条目变成可执行的卡片

/to-issues 处理的是你自己从 PRD 拆出来的东西，那些已经是 agent-ready 的；这个技能处理从外面进来的：bug 报告、用户反馈、别人提的需求。不要对 /to-issues 产出的卡片做 triage。

角色（每条最后必须落到一个）

角色含义动作
ready复现/需求清楚，验收条件写得出来补全正文（复现步骤、期望、验收条件、影响面），打 ready，交给主线
needs-info缺关键信息，现在无法判断按下面的模板发一条评论，打 needs-info
bug-confirmed确实是 bug，但根因未定记下症状与最小复现，转 /diagnose
duplicate已有同一条评论指路 → 关闭
wontfix明确不做评论写清理由（对应哪条产品边界）→ 关闭

先看哪些需要处理

gh issue list --state open --limit 50 --json number,title,labels,createdAt,comments \
  --jq '.[] | select((.labels|map(.name)|index("ready")|not) and (.labels|map(.name)|index("needs-info")|not)) | "\(.number)\t\(.createdAt)\t\(.title)"'

处理一条

  1. 先复现 / 先理解：能不能按报告里的步骤重现？重现不了就明确说"我按 X 复现不了"，不要假装。
  2. 判断影响面：影响谁、会不会坏数据、有没有绕过办法、是不是老版本才有。
  3. 补成 agent-ready 的卡片：正文要写到"一个不共享本次对话上下文的子代理也能独立开工"的程度——复现步骤、期望行为、验收条件、涉及文件/模块、明确的非目标。这条标准与 /to-issues 一致。
  4. 标注 + 按角色行动（关闭时说明理由并指路）。

要信息的模板（needs-info）

需要更多信息才能判断这个条目。

**已知**：<他给了什么>
**还缺**：
- [ ] <最小复现步骤 / 版本号 / 配置 / 完整报错>
- [ ] <期望行为 vs 实际行为>

补齐后我会重新评估；如果这是老版本的问题，请先确认在最新 <版本/commit> 上仍然存在。

记录

每条处理完，在那个 issue 上留一条评论说明结论（角色 + 理由 + 下一步），不要只改标签——后来的人要能看懂"为什么这么判"。整批处理完，把新增的 ready / needs-info / wontfix 数量报给用户，并把 ready 的那些交给主线（一串有依赖关系的用 /loop-it，互不共享文件的用 /graph）。

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