playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / 000-jeremy-content-consistency-validator

000-jeremy-content-consistency-validator skill

/plugins/productivity/000-jeremy-content-consistency-validator/skills/000-jeremy-content-consistency-validator

This skill checks messaging consistency across website, GitHub, and docs, generating a markdown report with prioritized fixes.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill 000-jeremy-content-consistency-validator

Review the files below or copy the command above to add this skill to your agents.

Files (9)
SKILL.md
1.9 KB
---
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 <[email protected]>
license: MIT
---

# 000 Jeremy Content Consistency Validator

## Overview

This skill provides automated assistance for the described functionality.

## Prerequisites

- Access to website content (local build or deployed site)
- Access to GitHub repositories
- Local documentation in {baseDir}/docs/ or claudes-docs/
- WebFetch permissions for remote content

## Instructions

1. Identify and discover all content sources (website, GitHub, local docs)
2. Extract key messaging, features, versions from each source
3. Compare content systematically across sources
4. Identify critical discrepancies, warnings, and informational notes
5. Generate comprehensive Markdown report
6. Provide prioritized action items for consistency fixes

## Output

- Comprehensive consistency validation report in Markdown format
- Executive summary with discrepancy counts by severity
- Detailed comparison by source pairs (website vs GitHub, etc.)
- Terminology consistency matrix
- Prioritized action items with file locations and line numbers
- Reports saved to consistency-reports/YYYY-MM-DD-HH-MM-SS.md

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources

- Content consistency best practices
- Documentation style guides
- Version control strategies for content
- Multi-platform content management approaches

Overview

This skill validates messaging consistency across a website, GitHub repositories, and local documentation and produces a read-only discrepancy report. It helps teams find mixed messaging, outdated claims, and terminology drift so you can prioritize fixes. Designed for quick audits and regular content hygiene checks.

How this skill works

The validator discovers content sources (deployed site or local build, GitHub repos, and local docs directories) and extracts key messaging items such as feature descriptions, versions, and terminology. It runs pairwise comparisons, flags critical discrepancies and warnings, and produces a Markdown report with an executive summary, detailed diffs, and prioritized action items. Reports include file paths, line numbers, and a terminology consistency matrix for fast triage.

When to use it

  • Before a product launch or documentation release to ensure public messaging matches code and docs
  • During audits to detect mixed messaging across website, repo README, and local docs
  • When onboarding or reorganizing content to find outdated or duplicate statements
  • As part of periodic content hygiene checks or release checklists
  • After merges or content PRs to validate that wording and version tags stayed consistent

Best practices

  • Run the validator against a local build and the deployed site to catch build-time differences
  • Keep local docs under consistent directories (e.g., docs/ or claudes-docs/) so the tool can discover them reliably
  • Use consistent terminology and a maintained glossary to reduce false positives
  • Integrate the report into CI or a scheduled job and review prioritized action items within sprint planning
  • Treat the output as read-only guidance; update source files and re-run the check to verify fixes

Example use cases

  • Compare the marketing website feature copy with repository README and developer docs to reconcile feature lists
  • Detect mismatched version numbers between package metadata in GitHub and the published site
  • Generate a report for product managers showing critical messaging conflicts before a release
  • Audit multiple plugin repos to produce a single consistency report for an ecosystem
  • Locate inconsistent terminology across docs and produce a matrix to feed into style-guide updates

FAQ

What outputs does the validator produce?

A Markdown report with an executive summary, discrepancy counts by severity, detailed comparisons, a terminology matrix, and prioritized action items with file locations and line numbers.

Does the tool modify source files?

No. It generates read-only discrepancy reports. Fixes must be applied to sources manually or via a separate automated process.