| name | 000-jeremy-content-consistency-validator |
| description | Validate messaging consistency across website, GitHub repos, and local documentation generating read-only discrepancy reports. Use when checking content alignment or finding mixed messaging. Trigger with phrases like "check consistency", "validate documentation", or "audit messaging".
|
| allowed-tools | Read, WebFetch, WebSearch, Grep, Bash(diff:*), Bash(grep:*) |
| version | 1.0.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
| compatible-with | claude-code, codex, openclaw |
| tags | ["productivity","audit","000-jeremy"] |
Content Consistency Validator
Overview
Checks content for tone, terminology, formatting, and structural consistency across multiple documentation sources (websites, GitHub repos, local docs). Generates read-only discrepancy reports with severity-classified findings and actionable fix suggestions including file paths and line numbers.
Examples
- Pre-release audit: Before tagging a new version, run the validator to catch version mismatches between your README, docs site, and changelog — e.g., the website says v2.1.0 but the GitHub README still references v2.0.0.
- Post-rebrand check: After renaming a product or updating terminology (e.g., "plugin" to "extension"), validate that all docs, landing pages, and contributing guides use the new term consistently.
- Onboarding review: When a new contributor flags confusing docs, run a consistency check to surface contradictory feature claims, outdated contact info, or missing sections across your documentation sources.
Prerequisites
- Access to at least two content sources (website, GitHub repo, or local docs directory)
- WebFetch permissions configured for remote URLs (deployed sites, GitHub raw content)
- Local documentation stored in recognizable paths (
docs/, claudes-docs/, internal/)
Instructions
- Discover sources — scan for build directories (
dist/, build/, public/, out/, _site/), GitHub README/CONTRIBUTING files, and local doc folders:
find . -maxdepth 3 -name "README*" -o -name "CONTRIBUTING*" | head -20
ls -d docs/ claudes-docs/ internal/ 2>/dev/null
- Extract structured data from each source: version numbers, feature claims, product names, taglines, contact info, URLs, and technical requirements:
grep -rn 'v[0-9]\+\.[0-9]\+' docs/ README.md
grep -rn -i 'features\|capabilities' docs/ README.md
- Verify extraction — confirm at least 3 data points per source. If a source returns empty, check the Error Handling table before continuing.
- Build comparison matrix pairing each source against every other (website vs GitHub, website vs local docs, GitHub vs local docs):
