semantic-validation

Detect semantic misalignment between documentation and code implementation.

32|5|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/akaszubski/autonomous-dev --skill semantic-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semantic-validation
Source: https://github.com/akaszubski/autonomous-dev/tree/main/plugins/autonomous-dev/skills/semantic-validation
Command: npx skills add https://github.com/akaszubski/autonomous-dev --skill semantic-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

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)

Frequently Asked Questions about semantic-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect outdated documentation in my codebase?

Semantic validation automatically compares documented claims against actual code implementation to flag discrepancies. It identifies when README files, architectural descriptions, and API documentation no longer match the current codebase structure, catching drift that manual review often misses.

Can I find version mismatches across project files automatically?

Yes, semantic validation detects inconsistencies in version numbers across package.json, CHANGELOG.md, and other project files. It reports all synchronized failures, preventing user confusion and build errors before release.

What's the best way to validate architectural drift after a refactor?

Run semantic validation after major refactors to automatically verify that architectural diagrams and documented structure still match your current codebase. It outputs structured signals of severity, evidence, and actionable fixes for each discrepancy found.

When should I run documentation validation in my release workflow?

Run semantic validation before major releases to ensure documentation reflects the latest features and all version numbers are synchronized. It's also valuable after significant refactors or when auditing drift between documented and actual architecture.

What output does semantic validation provide?

Semantic validation produces a structured report identifying outdated docs, version mismatches, and architectural drift with severity levels, evidence from your code, and actionable fixes to align documentation with implementation.