$ loading_
Audit an entire docs corpus against code and propose precise fixes.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "docs-corpus-audit" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/apm/main/.apm/skills/docs-corpus-audit/SKILL.md 2. Save it as ~/.claude/skills/docs-corpus-audit/SKILL.md 3. Reload skills and tell me it's ready
Run a whole-corpus audit of the microsoft/apm documentation. Check each page against the current source code for stale claims, incorrect configuration, dead links, and TOC-related breakage. Output page-by-page surgical fix recommendations only, with no auto-commit or merge.
A corpus-wide audit report listing issues, evidence, and ready-to-apply revision suggestions by page.
We just refactored core microsoft/apm modules. Reground the entire documentation set by checking whether every page still matches current code behavior, APIs, parameters, and examples, then identify all drift and propose minimal edits.
A page-by-page drift list with mismatches, affected sections, and minimal patch text.
We just reshaped the documentation TOC. Perform a full-corpus check to find dead links, broken references, invalid navigation, and context mismatches caused by the restructure, then output repair suggestions by page.
A page-organized report of link and navigation issues with replacement links and suggested wording fixes.
The docs corpus drifts silently between releases. docs-sync catches
drift introduced by individual PRs at PR-open time. This skill catches
the accumulated drift that slips past per-PR review -- stale flag
names, dead nav links from past IA reshuffles, deprecation banners
that outlived their version targets, factual claims whose source-side
truth has moved.
The pattern is A1 PANEL + WAVE EXECUTION + S7 DETERMINISTIC TOOL BRIDGE + A8 ALIGNMENT LOOP + A9 SUPERVISED EXECUTION. The corpus is split into disjoint page scopes; one verifier subagent owns each scope; agents extract factual claims, S7-verify against source, apply surgical fixes inline. The orchestrator then runs an alignment-loop pass to re-verify that applied edits actually ground out true.
This skill is ADVISORY but ACTIONABLE: agents apply edits inline on a working branch. The orchestrator is the sole writer to git -- stages, commits, pushes. Maintainer reviews the resulting PR.
These two skills share substrate. Be explicit:
| Shared resource | Owner | Both use |
|---|---|---|
.apm/docs-index.yml (corpus map) | docs-sync | yes |
| doc-writer persona | shared | yes (per-page edits) |
| python-architect persona | shared | yes (S7 verification) |
| editorial-owner persona | shared | optional (voice pass at scale) |
| cdo persona | shared | yes (final synthesis) |
assets/panelist-return-schema.json | docs-sync (mirrored) | yes |
Trigger boundary (avoid DISPATCH COLLISION):
docs-sync triggers on a PR event ("PR opened/synchronized",
source-diff-driven).docs-corpus-audit triggers on a maintainer ask for a
WHOLE-CORPUS pass ("audit the corpus", "reground", "pre-release
sweep") -- no PR required, no diff required, the whole corpus
is the input.If a maintainer asks "review this PR's doc impact", route to
docs-sync. If they ask "audit all our docs" or "the docs feel
stale everywhere", route here.
uv run apm <verb> --help for CLI,
grep -n src/apm_cli/ for symbols, python -c "import ..." for
module shape, file-existence checks for nav links. Never assert
from LLM recall.git commit, git push, or gh pr <write>. Orchestrator
commits per wave; pushes once per session.Reuse docs-sync's personas. Do NOT invent a one-off "grounding- verifier" role; that's R3 EXTRACT in reverse.
| Role | Persona | Always active? |
|---|---|---|
| Per-scope verifier+editor | python-architect (S7) and doc-writer (edits), bundled into one subagent prompt per scope | Yes -- one per page scope, parallel fan-out |
…
Triage microsoft/apm issues and produce one unified resolution comment.
Verify whether answers are supported by documents and flag grounding issues.
Turn docs impact verdicts into page-by-page, section-level sync task briefs.
Guide APM positioning, release communication, and breaking-change strategy decisions.
Improve CLI output, logs, errors, and terminal diagnostic user experience.
Triage APM issues in batches and drive approved ones to mergeable PRs.
Assess PR documentation impact and produce actionable update guidance every time.
Classify PR doc impact to decide whether documentation updates are needed.
Run a multi-expert advisory review for labelled microsoft/apm pull requests.
Write complete, evidence-backed PR descriptions for microsoft/apm pull requests.
Audit your environment and recommend the best Claude Code setup
Plan doc TOC changes and outline stubs when PRs require structural updates.