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.
Scanned 2/12/2026
Install via CLI
openskills install majiayu000/claude-skill-registry---
name: doc-validator
description: 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.
---
# Documentation Validator
## Validation Checks
### 1. Completeness
- [ ] Installation instructions present
- [ ] Usage examples provided
- [ ] API reference complete (if applicable)
- [ ] Troubleshooting section exists
- [ ] Contributing guidelines (if open source)
### 2. Accuracy
- [ ] Code examples are runnable
- [ ] Commands match actual CLI
- [ ] File paths exist
- [ ] Version numbers match package.json/pyproject.toml
- [ ] Links are not broken
### 3. Consistency
- [ ] Terminology is consistent
- [ ] Code style in examples matches project
- [ ] Formatting is uniform
- [ ] Table of contents matches headings
### 4. Quality
- [ ] No spelling/grammar errors
- [ ] Clear and concise language
- [ ] Proper markdown formatting
- [ ] Code blocks have language hints
## Process
1. **Find documentation files**
```bash
find . -name "*.md" -o -name "*.rst"
```
2. **Read and analyze**
- Check structure (headings, sections)
- Verify code examples
- Validate links and references
3. **Cross-reference with code**
- Compare CLI commands with actual implementation
- Verify file paths exist
- Check version numbers
4. **Report findings**
- List issues by category
- Suggest improvements
- Provide examples of fixes
## Examples
✅ **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)
## Supporting Files
For detailed validation rules, see [references/validation-rules.md](references/validation-rules.md).
No comments yet. Be the first to comment!
Create Mermaid diagrams for flowcharts, sequences, ERDs, and
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.