OSS Doc Audit

Audit public docs against live code and repo policy.

This is not a prose-polish skill. Factual correctness, active-stack alignment, and functioning guardrails come first. Style cleanup is secondary — for prose-level slop (emdashes, "Here's why", forced enthusiasm), hand off to the de-slopify skill after factual drift is resolved. The two skills compose: this one decides whether a doc should exist and be accurate; de-slopify decides whether the surviving prose sounds human.

On Trigger

Start the first progress update with:

Using oss-doc-audit ...

If the repo is large, split the read-only audit into parallel concerns after the baseline scan: