Validate documentation files for completeness, accuracy, and consistency with the codebase. Use when user mentions "check documentation", "validate docs", "is the README up to date?", requests documentation review, says "docs are wrong" or "fix the docs", or is working on documentation improvements. Covers README files, API docs, CHANGELOG, and any markdown documentation.
Validates documentation for completeness, accuracy, and consistency with the codebase. Triggered when you ask to check, validate, or review docs, or mention documentation issues. Checks README, API docs, CHANGELOG, and markdown files against actual code, commands, and file paths.
/plugin marketplace add poindexter12/waypoint/plugin install claire@waypoint-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
REFERENCE.mdFind documentation files
find . -name "*.md" -o -name "*.rst"
Read and analyze
Cross-reference with code
Report findings
✅ Good trigger: "Check if our README is complete" ✅ Good trigger: "Validate the API documentation" ✅ Good trigger: "The docs mention /old-command but I don't see it in the code"
❌ Bad trigger: "Write new documentation" (creation, not validation) ❌ Bad trigger: "Fix typo in line 42" (too specific, not validation)
For detailed validation rules, see REFERENCE.md.