$ loading_
对 microsoft/apm 的标记 PR 发起多专家联合审查并给出综合建议
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "apm-review-panel" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/apm/main/packages/apm-review-panel/SKILL.md 2. 保存为 ~/.claude/skills/apm-review-panel/SKILL.md 3. 装好后重载技能，告诉我可以用了
请对 microsoft/apm 中这个已标记的非简单 PR 运行 apm-review-panel，重点审查架构影响、CLI 日志、开发者体验、供应链安全与发布风险，并输出一条综合建议评论。
一条汇总多位专家意见的 PR 建议评论，列出主要发现、优先级后续事项与建议是否可发布。
请对这个已标记且修改了 src/ 的 PR 运行 apm-review-panel，除常规专家外重点检查测试覆盖充分性、回归风险和实现质量，最后只输出一条建议评论。
一条包含测试覆盖评估、风险提示和改进建议的综合评论，不添加结论标签或阻止合并。
请对这个已标记 PR 运行 apm-review-panel。该变更同时影响用户文档和运行性能，请纳入文档编写与性能专家视角，综合判断是否适合当前版本发布，并给出后续优先级建议。
一条结合文档、性能及其他专家意见的 CEO 式综合建议，帮助维护者权衡发布决策。
The panel is FAN-OUT + SYNTHESIZER. Each persona runs in its own agent
thread (via the task tool) and returns JSON matching
assets/panelist-return-schema.json. The orchestrator schema-validates
each return, hands all returns to the apm-ceo synthesizer (also a task
thread, returns JSON matching assets/ceo-return-schema.json), then
renders ONE recommendation comment from assets/recommendation-template.md.
This skill is ADVISORY by design. It does not compute a binary verdict, it does not apply verdict labels, and it does not gate merge. The panel surfaces findings; the maintainer and the PR author decide ship.
APPROVE / REJECT,
no panel-approved / panel-rejected label, no deterministic verdict
computation. The CEO returns a ship_recommendation.stance (ship_now
/ ship_with_followups / needs_discussion / needs_rework); this is
prose for the human reviewer, never auto-applied as a label or status
check. This is the architectural fix for the previous regime's
over-strictness: removing the binary gate removes the incentive for
panelists to inflate defensively.required[]severity: blocking | recommended | nit. blocking is the highest
signal a panelist can send and renders prominently in the comment; it
still does not block merge. recommended is the default for substantive
feedback. nit is one-line polish. The orchestrator never reads
severity to gate anything.add-comment and one remove-labels call. The
remove-labels call always sweeps panel-review (trigger
idempotency) AND defensively removes panel-approved /
panel-rejected if present (legacy verdict labels from the
pre-advisory regime; they have no meaning here and would mislead
readers if left on a PR after a fresh advisory pass). NO add-labels
call -- there are no verdict labels to apply. Panelist subagents and
the CEO subagent return JSON only and MUST NOT call any gh write
command, post comments, apply labels, or touch the PR state.assets/recommendation-template.md after all subagents
return.| Agent | Role | Always active? |
|---|---|---|
| Python Architect | Architectural Reviewer + supplies mermaid diagrams | Yes |
| CLI Logging Expert | Output UX Reviewer | Yes |
| DevX UX Expert | Package-Manager UX | Yes |
| Supply Chain Security Expert | Threat-Model Reviewer | Yes |
| OSS Growth Hacker | Adoption Strategist | Yes |
| Auth Expert | Auth / Token Reviewer | Conditional (see below) |
| Doc Writer | Documentation Reviewer | Conditional (see below) |
| Test Coverage Expert | Test-Presence Reviewer (paired with DevX UX) | Yes (skipped only on docs-only PRs -- see below) |
| Performance Expert | Package-Manager Performance Reviewer | Conditional (see below) |
| APM CEO | Strategic Arbiter / Synthesizer | Yes |
apm-review-panel SKILL (orchestrator thread)
|
FAN-OUT via task tool (panelists in parallel)
|
+-----+-------+-------+-----+-----+------+-----------+----------+
v v v v v v v v v (cond.)
py cli dx-ux sec grw auth doc-writer test-cov
…
优化 APM 代码库中的 CLI 输出、日志提示与诊断信息体验
为 microsoft/apm 的拉取请求自动撰写结构完整、证据充分的 PR 描述。