$ loading_
帮助开发团队快速分诊 microsoft/apm 新开或待分诊问题并生成统一处理意见
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "apm-triage-panel" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/apm/main/packages/apm-triage-panel/SKILL.md 2. 保存为 ~/.claude/skills/apm-triage-panel/SKILL.md 3. 装好后重载技能，告诉我可以用了
请分诊 microsoft/apm 中这个新开 issue，输出一条综合评论，包含分诊结论、建议标签、里程碑和下一步行动。
一条可直接发布到 issue 的分诊评论，明确是否接受、应打哪些标签、归属里程碑及后续处理建议。
请针对这个被重新打开的 microsoft/apm issue 进行分诊，结合上下文给出单条评论，包含处理决定、标签集合、里程碑和建议动作。
一条整合历史讨论与当前状态的评论，用于指导维护者继续修复、补充信息或关闭处理。
请分诊这个带有 status/needs-triage 标签的 microsoft/apm issue，输出一个最终分诊评论，涵盖结论、标签、里程碑和下一步建议。
一条结构清晰的分诊结果，帮助团队快速完成标签整理和后续任务分配。
The panel is fixed at 3 mandatory specialist lenses + up to 3 conditional lenses + 1 arbiter lens = up to 6 active persona sections in one triage comment (3 mandatory + 3 conditional). You play each lens in turn from inside a single agent loop (progressive-disclosure skill model -- no sub-agent dispatch). Routing chooses which lenses execute; it never changes which headings appear in the final comment.
This skill mirrors the apm-review-panel orchestration shape on
purpose. Same single-comment discipline, same completeness gate, same
persona-pass procedure -- only the personas, the rubric, and the
output template differ.
| Agent | Persona | Always active? |
|---|---|---|
| DevX UX Expert | User-Need Reviewer | Yes |
| Supply Chain Security Expert | Risk-Surface Reviewer | Yes |
| APM CEO | Triage Arbiter | Yes (always arbitrates) |
| OSS Growth Hacker | Contributor-Tone Reviewer | Conditional (see below) |
| Python Architect | Architecture Reviewer | Conditional (see below) |
| Doc Writer | Documentation Reviewer | Conditional (see below) |
Skipped by default: CLI Logging Expert, Auth Expert. Triage operates
on issue intent, not on diffs -- those personas are invoked downstream
by apm-review-panel once a PR exists.
devx-ux-expert supply-chain-security-expert
\_______________________/
|
| <-- python-architect (conditional; design /
| architecture / new primitive / new schema)
|
| <-- doc-writer (conditional; docs work or
| user-facing change that needs new doc pages)
v
apm-ceo <---- oss-growth-hacker
(final call / arbiter) (conditional; tunes tone
when author is new)
status/needs-design when warranted.Three personas are conditional: OSS Growth Hacker, Python Architect, and Doc Writer. Each follows the same shape: an explicit YES/NO activation rule plus an inactive-reason fallback. Maximum lenses in a single triage = 6 (3 mandatory + 3 conditional).
Activate oss-growth-hacker if either rule below matches.
Fast-path author trigger. Activate the Growth Hacker lens immediately when the issue's author meets ANY of:
author_association is FIRST_TIME_CONTRIBUTOR,
FIRST_TIMER, or NONE against microsoft/apm.microsoft/apm.Fallback self-check. If author signals are ambiguous, answer this before activating the lens:
Would the warmth, framing, or pointer-set in the reply meaningfully
…
优化 APM 代码库中的 CLI 输出、日志提示与诊断信息体验
对 microsoft/apm 的标记 PR 发起多专家联合审查并给出综合建议