← ClaudeAtlas

documentation-auditorlisted

Use when the user explicitly asks to audit documentation integrity, check docs against code, find documentation discrepancies, or verify whether AI-context documentation still matches repository evidence. This skill is manually invoked and is distinct from task Finalization. It must investigate code/tests/scripts/schemas as source-of-truth evidence when docs may be stale.
escogido/knowledge-cairn · ★ 0 · Data & Documents · score 69
Install: claude install-skill escogido/knowledge-cairn
# Documentation Auditor ## Purpose Perform an out-of-cycle documentation integrity audit. This skill checks whether AI-context documentation is internally consistent and whether it matches current repository evidence, excluding `../../../ai-context/archive/`. It may inspect code, tests, scripts, schemas, generated artifacts, and relevant evidence to determine which documentation is stale. ## Distinction From Finalization Finalization answers: > What changed during the completed task, and which durable docs must be updated because of that task? Documentation Audit answers: > Do the docs currently contradict each other or the code/repository evidence, regardless of the current task? Do not use this skill as a substitute for ordinary task Finalization. Do not automatically run this skill during Finalization. ## Read-Only Rules This skill is read-only. The skill may propose exact documentation patches, but must not apply changes. If the user asks to apply fixes, the auditor still reports only; applying targeted documentation fixes is a separate invoker action after the audit, with explicit user authorization. A proposed patch lands only on what the project wrote: its General, Situational, and Operational content, the indexes that grow with it, and its own documentation outside `../../../ai-context/`. Never propose one against Cairn's own shipped text, which the project did not write and an upgrade replaces, so a local patch forks it silently: - `../../../AGENTS.md`