将文档影响判定结果细化为逐页逐段的同步执行任务简报。
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "docs-impact-localizer" 技能: 1. 下载 https://raw.githubusercontent.com/microsoft/apm/main/.agents/skills/docs-impact-localizer/SKILL.md 2. 保存为 ~/.claude/skills/docs-impact-localizer/SKILL.md 3. 装好后重载技能,告诉我可以用了
docs-impact-classifier 已返回 verdict=in_place。请读取候选页面列表,抓取每页当前内容,定位需要修改的具体章节,并输出 docs-sync panel 可直接分发的逐页任务简报。
输出按页面组织的任务清单,说明每页需修改的章节、修改范围与执行重点。
基于 in_place 判定和候选页面列表,检查每个文档页面内容,只保留真正受影响的章节;如果某页无需改动,请明确标记为无需处理,并为其余页面生成简明任务说明。
输出去噪后的逐页结果,包含无需处理页面标记与受影响页面的章节级任务说明。
请把已判定为 in_place 的文档影响结果转成 docs-sync panel 可执行的任务输入:逐页列出目标页面、受影响章节、建议修改方向,以及需要同步关注的上下文说明。
输出结构化的逐页任务简报,便于后续面板并行分发与执行。
Single responsibility: given a list of candidate pages from the classifier, produce a per-page task brief the docs-sync panel can fan out against.
You are NOT the verdict-maker (classifier owns that). You are NOT the writer (doc-writer owns that). You are the work planner.
The docs-sync orchestrator invokes you ONLY when the classifier
returned verdict: in_place. For no_change you don't run.
For structural the architect runs first; you may run after, scoped
to existing pages that need amendment.
scope_pages[] from the classifiergh pr diff $PR).apm/docs-index.yml (per-page metadata)For each path in scope_pages[], read the file. Pages are typically
3-10 KB; total budget for this step is bounded by the candidate
count (the classifier should have kept it to <= 6).
For each page, identify the SPECIFIC section(s) that need to change:
lines 120-145 not the whole pageThe output is a sections_to_edit[] per page, where each entry is:
page: docs/src/content/docs/consumer/install.md
sections_to_edit:
- section: "## From Git"
line_range: [120, 145]
diff_symbol: "--no-cache flag"
edit_kind: add | modify | remove
rationale: "the new --no-cache flag is documented nowhere; section already lists other flags so this is the natural home"
If two pages document the same symbol and the diff changes the symbol's behaviour, BOTH pages need an edit AND they must stay consistent. Flag this in the brief so the CDO synthesizer knows to cross-check coherence between the two redrafts:
cross_page_constraint:
pages: [path1, path2]
shared_symbol: "apm install --target"
consistency_required: "both pages must reflect the same default value"
Return JSON with this shape (one entry per page in scope_pages[]):
{
"tasks": [
{
"page": "docs/src/content/docs/consumer/install.md",
"persona_owner": "consumer",
"promise": 1,
"sections_to_edit": [
{
"section": "## From Git",
"line_range": [120, 145],
"diff_symbol": "--no-cache flag",
"edit_kind": "add",
"rationale": "..."
}
],
"verify_claims": [
{"claim": "the flag is named --no-cache", "verify_with": "apm install --help"},
{"claim": "the flag is documented in click.option decorator", "verify_with": "grep -n no-cache src/apm_cli/commands/install.py"}
]
}
],
"cross_page_constraints": [
{"pages": [...], "shared_symbol": "...", "consistency_required": "..."}
],
"estimated_panel_calls": 8
}
The verify_claims[] per page is consumed by the python-architect
panelist -- it tells the verifier WHICH claims need a S7 tool-call
check (run apm install --help, grep the source) rather than
prose-trusting.
Return a SINGLE JSON document matching the schema in Step 4 as the final message of your task. No prose around the JSON.
verify_claims[] -- that's the S7 tool-bridge hook; the verifier needs it.scope_pages[] -- that's the classifier's job, not yours. If you think the classifier missed a page, return an extra field localizer_concern instead of expanding scope unilaterally.优化 APM 代码库中的 CLI 输出、日志提示与诊断信息体验
快速判断 PR 变更对文档的影响级别,决定是否需要更新或重构文档。