What problem does it solve?
Documentation drifts silently between releases: CLI flags get renamed, nav links die after IA reshuffles, and deprecation banners outlive their version targets. Per-PR review only catches drift introduced by that PR, so accumulated staleness across the whole corpus goes unnoticed until users hit broken docs.
Core Features & Use Cases
- Whole-corpus regrounding: Partitions the docs corpus into disjoint page scopes and dispatches parallel verifier subagents that extract every factual claim (CLI flags, file paths, symbols, nav links) and verify each against deterministic source such as
uv run apm <verb> --help and grep over src/apm_cli/.
- Surgical inline fixes: Applies 1-3 line voice-preserving patches per drift on a working branch, with a single-writer git interlock so only the orchestrator commits and pushes for maintainer PR review.
- Cross-corpus drift scanning: Runs a deterministic shell script to catch patterns invisible to per-page agents, including dead IA-reshuffle links, stale deprecation version targets, absolute base links, and non-ASCII leaks.
- Use Case: Before cutting release v0.16, ask for a pre-release docs sweep; the skill audits all ~112 pages in waves, verifies claims against code, fixes drift, and opens a PR with a per-wave summary in roughly 10 minutes.
Quick Start
Ask the agent to audit the entire docs corpus and reground every claim against the current source code on a working branch.
