plugins/autonomous-dev/skills/archived/semantic-validation/SKILL.md
GenAI-powered semantic validation - detects outdated docs, version mismatches, and architectural drift
npx skillsauth add akaszubski/autonomous-dev semantic-validationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Purpose: Use GenAI to validate that documentation accurately reflects implementation, catching issues that structural validation misses.
This skill provides comprehensive guidance on semantic validation. For detailed patterns and implementation examples, see the documentation files in docs/.
Key Topics:
See: Documentation files in docs/ directory for complete details
| Topic | Details |
|-------|---------|
| Detailed Guide 1 | docs/detailed-guide-1.md |
| Detailed Guide 2 | docs/detailed-guide-2.md |
| Detailed Guide 3 | docs/detailed-guide-3.md |
This skill uses progressive disclosure to prevent context bloat:
docs/*.md files with implementation details (loaded on-demand)Available Documentation:
docs/detailed-guide-1.md - Detailed implementation guidedocs/detailed-guide-2.md - Detailed implementation guidedocs/detailed-guide-3.md - Detailed implementation guideRelated Skills:
Related Tools:
development
One topic, one home. Routes content to its canonical store (CLAUDE.md, PROJECT.md, MEMORY.md, docs/, memory/) and audits for duplication. TRIGGER when: auditing CLAUDE.md/PROJECT.md/MEMORY.md sizes, deduplicating docs, applying the content-allocation pattern to a new repo, running /align --content. DO NOT TRIGGER when: implementing features, writing tests, routine code edits, debugging.
development
GenAI-first testing with structural assertions, congruence validation, and tier-based test structure. Use when writing tests, setting up test infrastructure, or validating coverage. TRIGGER when: test, pytest, coverage, TDD, test patterns, congruence, validation. DO NOT TRIGGER when: production code implementation, documentation, config-only changes.
testing
Prompt engineering patterns for writing agent prompts and skill files — constraint budgets, register shifting, HARD GATE patterns, anti-personas. Use when writing or reviewing agents/*.md or skills/*/SKILL.md. TRIGGER when: agent prompt, skill file, prompt engineering, model-tier compensation, HARD GATE, prompt quality. DO NOT TRIGGER when: user-facing docs, README, CHANGELOG, config files.
testing
7-step planning workflow for pre-implementation design. Enforced by plan_gate hook, critiqued by plan-critic agent. Use when creating plans, design documents, or architecture decisions before implementation. TRIGGER when: plan, planning, /plan, design document, architecture decision. DO NOT TRIGGER when: implementation, coding, testing.