← ClaudeAtlas

documentation-updatelisted

Audits a documentation file line-by-line against the actual codebase, proving every factual claim with source file and line number citations. Produces a structured evidence table, applies corrections for inaccuracies, then verifies corrections are themselves accurate. Use when a user asks to review, audit, refresh, or update a documentation file, or says a doc is outdated.
stempeck/agentfactory · ★ 0 · Data & Documents · score 65
Install: claude install-skill stempeck/agentfactory
# Documentation Audit and Update Systematically verify every factual claim in a target documentation file against the actual codebase. No heuristics, no skimming — every line gets a source citation or an inaccuracy flag. ## Workflow Copy this checklist and track progress: ``` Audit Progress: - [ ] Phase 1: Read and chunk the target document - [ ] Phase 2: Launch parallel verification agents (one per chunk) - [ ] Phase 3: Compile findings and spot-check subagent verdicts - [ ] Phase 3.5: Cross-reference scan (grep full doc for inaccurate entities) - [ ] Phase 4: Present findings to user, get approval - [ ] Phase 5: Apply corrections - [ ] Phase 5.5: Ripple scan (grep full doc for every changed term) - [ ] Phase 6: Verify corrections against source code ``` ### Phase 1: Read and chunk the target document Read the target file. Split it into chunks of ~50 lines. Record the line ranges. The goal is to produce chunks small enough that a verification agent can be exhaustive about every claim in its range, and large enough to avoid excessive agent overhead. If the user asks about a specific section, chunk that section. Phase 3.5 will catch the same claims appearing elsewhere in the document — you do not need to audit the entire file to get full coverage. ### Phase 2: Launch parallel verification agents Launch one `Explore` subagent per chunk, **all in parallel**. Each agent gets this mandate: ``` You are auditing <FILE> lines <START>-<END> against the actual codebase at <R