用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/projectbluefin/testsuite --skill triage命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | triage |
| version | 1.0 |
| last_updated | 2026-07-20 |
| id | triage |
| one_line_purpose | Triage testsuite issues and pull requests with the canonical label workflow. |
| entry_point | docs/skills/meta/triage/SKILL.md |
| category | meta |
| mcp_compliance_level | partial |
| status | active |
| dependencies | [] |
| tags | ["triage","labels","issues"] |
| description | Issue triage rules and lifecycle labels for this repo. Load when triaging open issues or backlog PRs. |
| metadata | {"type":"pattern","audience":"agents","maturity":"stable"} |
projectbluefin/testsuite uses the canonical factory label contract from
common/docs/skills/label-workflow.md.
That document is authoritative; this skill only covers what is specific to
testsuite. Good triage means every open issue carries exactly one numbered
workflow label, stale work is closed, and agents never waste time on blocked or
already-finished items.
Trust the machines: workflows own state, humans provide intent. Do not invent a second state machine with comments, custom labels, or local scripts.
docs/skills/meta/human-gates/SKILL.md)projectbluefin/lab or another repo (file/link there)Do not reconstruct the actionable queue by grepping labels. The Hive exposes the single source of truth:
~/.agents/skills/hive-todos/scripts/hive-todos.sh --repo testsuite --summary
~/.agents/skills/hive-todos/scripts/hive-todos.sh --repo testsuite --top 20
~/.agents/skills/hive-todos/scripts/hive-todos.sh --repo testsuite --queued --top 10
~/.agents/skills/hive-todos/scripts/hive-todos.sh --prs --top 10
Combine filters freely (--repo, --label, --top, --json).
Check current labels before editing:
gh label list --repo projectbluefin/testsuite
The seven canonical workflow labels are the only lifecycle state:
| Label | Meaning |
|---|---|
1-triage | New work awaiting triage |
2-discussing | Discussion or design clarification needed |
3-human-queue | Admitted to the human-maintained queue |
3-clanker-queue | Admitted to the agent-maintained queue — this is what agents claim |
4-review | Pull request awaiting review |
blocked | Waiting on human input or an external dependency (overlay) |
hold | Intentionally paused (overlay) |
Exactly one numbered label per issue, with blocked or hold as an optional
overlay. testsuite additionally carries repository-local, non-lifecycle labels
(kde, runner, dependencies, javascript) applied by automation; they
describe scope, not state.
Older testsuite docs referenced
status/queued,status/triage,status/hold,status/claimed,pr/needs-review,automerge,test-quality,coverage-gap,structural, andsource:*. None of these exist on the repository. Do not create them — adding a label is a governance action requiring human sign-off. Record classification detail in the issue body or project fields instead.
Read the queue. Use the Hive summary plus raw GitHub lists:
gh issue list --repo projectbluefin/testsuite --state open --limit 200
gh pr list --repo projectbluefin/testsuite --state open --limit 200
Inspect stale issues. For anything older than a few weeks, read the body, recent comments, and linked commits/PRs. Verify against the repo:
git log --oneline -- tests/<suite>/features/<feature>.feature
git show <commit> -- tests/<suite>/features/steps/steps.py
Apply exactly one numbered label per issue. An issue should not sit
unlabeled. Use 1-triage, 2-discussing, 3-human-queue, or
3-clanker-queue, plus blocked/hold as an overlay when applicable.
Classification detail (test quality, coverage gap, structural) belongs in the
issue body, not in a new label.
Close completed/duplicate issues. Use evidence from code or comments. Close quietly — labels and git history are the audit trail.
GH_REPO=projectbluefin/testsuite gh issue close <number>
Remove queue labels from closed issues so the Hive stays accurate:
GH_REPO=projectbluefin/testsuite gh issue edit <number> --remove-label "3-clanker-queue"
Triage PRs. Classification only — approving and merging are human
authority (see docs/skills/meta/human-gates/SKILL.md).
4-reviewautomerge labelAGENTS.md)Re-check the queue. Run the Hive summary again and confirm the counts match your changes.
| Situation | Label | Notes |
|---|---|---|
| Fix is in testsuite, clear next step, no human gate | 3-clanker-queue | Ready for an agent to claim |
Missing scenario or @future stub | 3-clanker-queue | Update suite-map.md and docs/qa-review.md when implemented |
| Broken step/assertion | 3-clanker-queue | Reference the failing step in the body |
| Harness/CI issue | 3-clanker-queue or 3-human-queue | May need a split PR to projectbluefin/lab |
| Upstream image regression (bazzite extensions, composefs caps, MIME defaults) | blocked | Do not fix in testsuite; link the tracking issue |
| Needs design or cross-repo decision | 2-discussing | Wait for the human decision |
| Migration/UEFI workflow paused by policy | hold | Blocked by maintainer policy or spike |
| Human should do it | 3-human-queue | Not agent-claimable |
3-clanker-queue. If a human must
decide, use 2-discussing or 3-human-queue.ublue-os/*, cncf/*, or homebrew/*.At the end of a triage session:
3-clanker-queue or 3-human-queuegh label list --repo projectbluefin/testsuite shows only the seven
canonical labels plus repository-local automation labelshive-todos --repo testsuite --summary reflects the expected queue4-review or has a known blocker