菜单
Runs new and updated pull requests through the triage checklist (size, description, failing checks) and proposes labels and at most one comment per pull request. Use on the triage routine or when asked to triage pull requests.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/freema/drobek-bot --skill triage命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Writes the morning GitHub briefing (failing pull requests, review requests, open issues) across the person's repositories, with proposed comments kept as drafts. Use when asked for a GitHub briefing, what needs review, or what is failing.
Writes the morning inbox briefing from the webmail tab in the person's browser. Use when asked for a briefing, a summary of the inbox, or what needs an answer today.
Checks Sentry for issues that are new or have regressed since the last run, groups them by cause and drafts an incident note. Use on the hourly routine or when asked what is breaking right now.
正在显示 SKILL.md
| name | triage |
| description | Runs new and updated pull requests through the triage checklist (size, description, failing checks) and proposes labels and at most one comment per pull request. Use on the triage routine or when asked to triage pull requests. |
memory/progress.md: the repositories to watch and the pull requests already triaged, with the head commit each was triaged at.list_pull_requests with state: open, sorted by updated. A pull request is work when it is not in the progress file or its head commit changed since it was triaged. Skip drafts and pull requests opened by bots.pull_request_read with method: get, get_files and get_status for each pull request that is work, then:| Check | Rule | Label | Comment |
|---|---|---|---|
| Size | more than 400 changed lines or more than 20 files | size/large | none |
| Size | 400 changed lines or fewer | size/small | none |
| Description | body empty or under 30 characters, or no line saying what and why | needs-description | one comment asking for what changed, why, and how it was verified |
| Checks | at least one check failing or errored | ci-failing | one comment naming the failing check |
| Checks | checks still pending | none | none; look again next run |
issue_write (labels only, never state, title or body) and the comment through add_issue_comment. Each call asks; say in one line what you are about to send before you call.label_write asks; if the person denies, mention the missing label in the run report instead.memory/runs/<YYYY-MM-DD>.md and rewrite memory/progress.md with the head commit of every pull request triaged.memory/progress.md: report it and stop; the person fills the list in.# Triage <YYYY-MM-DD> <HH:MM>
- <owner/repo>#<n> <title>: <labels> — comment: <yes/no> — <findings>
Nothing to say: #<n>, #<n>
Waiting: <count> more