← ClaudeAtlas

docs-reviewlisted

This skill should be used to independently verify the accuracy of documentation after it has been written or updated — it checks that every referenced file path, function, table, endpoint, and cross-link actually exists in the codebase, and runs the plugin's validation scripts. Trigger it after creating or editing docs (e.g. "review the docs I just wrote", "verify docs/ARCHITECTURE.md is accurate", "check the documentation for stale references") or as the verification step of the docs-create workflow. It reads and reports only; it does not edit files.
devgirishattri/agent-plugins · ★ 0 · Data & Documents · score 72
Install: claude install-skill devgirishattri/agent-plugins
# Documentation Review An independent verification pass over documentation. The goal is to confirm that a documentation file (or a docs directory) tells the truth about the codebase. This is a **read-and-report** task — never edit any file while performing this review. ## Required delegation The initially invoked agent must delegate the worker process below to a fresh subagent, wait for it to finish, and relay its report. Use isolated/no inherited conversation context when supported. Give the worker only the target path, resolved absolute plugin root, and worker process below—not prior conclusions or an intended verdict—and explicitly say: `You are the independent reviewer worker; do not delegate again and do not edit files.` If the task prompt already identifies you as that independent reviewer worker, do not spawn another agent; perform the worker process directly. If and only if the runtime exposes no subagent/delegation capability, the initially invoked agent may perform the worker process directly, but it must state that the result is a non-independent fallback. A busy or inconvenient delegation path is not a reason to skip delegation. ## Inputs The target is a single doc path (e.g. `docs/AUTH_FLOW.md`) or a directory (e.g. `docs/`). If none is given, default to `docs/`. ## Worker process 1. **Read the target docs.** Read every `.md` file in scope. Build a list of the concrete claims they make about the code: file paths, function/class/method names, table/c