review-docs

Run the review-docs skill, which extracts every external URL from your markdown files and HTTP-checks each one, then verifies that file paths and code symbols mentioned in docs still exist in the repository. Results are written to a dated report under docs/appendix/reviews/.

Use the included cdp-shot.mjs helper, which drives the browser over the Chrome DevTools Protocol instead of the one-shot --screenshot flag. It navigates, waits a fixed time, then captures the full scrollable page regardless of network-idle state, which is what causes the hang on mkdocs-material pages.

The skill uses the gemini CLI with native filesystem access for the full-project structure pass, gemini-2.5-pro via the llm CLI for vision-based screenshot analysis, and gemini-2.5-flash for isolated per-page content and fact-checking passes.

Yes, pass the page path as an argument, for example /review-docs docs/path/to/page.md. Single-page mode skips the project-wide structure pass and runs only the visual, content, and factual checks for that page.

The persona has no domain knowledge, so it flags acronyms, assumed concepts, and logical leaps that a familiar reviewer would gloss over. This simulates a genuine cold read of the documentation by a new user.

Chrome caps a single screenshot at roughly 16000 pixels in height, so very tall pages get clipped and the helper logs the clip. For those pages you must split the review or capture the lower half separately.