semantic-validation

What problem does it solve?

Manual documentation review is slow and error-prone, leading to outdated docs, version mismatches, and architectural drift. This skill automates the detection of these inconsistencies, ensuring your project's documentation always reflects reality.

Core Features & Use Cases

• Outdated Documentation: Automatically compares documented claims with actual code implementation, flagging discrepancies.
• Version Mismatches: Detects and reports inconsistencies in version numbers across various project files (e.g., package.json, CHANGELOG.md).
• Architecture Drift: Identifies when documented architecture no longer matches the current codebase structure.
• Use Case: Before a major release, run this skill to ensure your README.md accurately reflects the latest features and that all version numbers are synchronized, preventing user confusion and build errors.
• Use Case: After a significant refactor, automatically validate that architectural diagrams and descriptions in your documentation are still current.

Quick Start

This skill is typically auto-invoked as part of a larger workflow.

To manually trigger a semantic validation report:

/align-project

(Select Phase 2: Semantic Validation from the options presented)