validate-docs-implementation

Compares implementation code against documentation to detect and fix inconsistencies.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/FahadImdad/Nexus-Fahad --skill validate-docs-implementation-fahadimdad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-docs-implementation
Source: https://github.com/FahadImdad/Nexus-Fahad/tree/main/00-system/skills/system/validate-docs-implementation
Command: npx skills add https://github.com/FahadImdad/Nexus-Fahad --skill validate-docs-implementation-fahadimdad

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Documentation drifts out of sync with code after refactors, causing user confusion and wasted debugging time. This Skill systematically finds and fixes mismatches between what the implementation actually does and what the docs claim. ## Core Features & Use Cases - Implementation Analysis: Reads scripts and code to establish ground truth about files, folders, and behavior created. - Exhaustive Search: Uses grep patterns to find every reference to outdated file names, folder structures, and counts across all documentation. - Systematic Fixing & Verification: Updates mismatches by priority, re-searches to confirm old terms are gone, and generates a permanent validation report. - Use Case: After renaming planning files from design.md/tasks.md to plan.md/steps.md, run this Skill to update 6 documentation files with 23 fixes and produce a full audit report. ## Quick Start Ask the AI to validate the docs for init_project.py and fix any documentation mismatches it finds.

Frequently Asked Questions about validate-docs-implementation

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

FAQPage Schema
How do I check if documentation matches my code?

Run the validation workflow: read the implementation to establish ground truth, grep the documentation for outdated terms, categorize mismatches by type, then fix and verify. The Skill automates this five-step process and produces a report.

What kinds of documentation mismatches can be detected?

The Skill detects file name mismatches, folder structure mismatches, incorrect counts, missing information about created artifacts, obsolete references to removed features, and inconsistent terminology across documents.

Where are validation reports saved?

Reports are saved to a user-configured location stored in config.yaml, defaulting to options like 04-workspace/validation-reports/ or 01-memory/validation-reports/. On first use, the Skill prompts you to choose and remembers your preference.

Can I generate a validation report automatically from a script?

Yes, the included generate_report.py script builds a formatted Markdown report from a JSON data file, calculating statistics like total changes and files updated. Run it with --data and --output-dir arguments.

How does the Skill verify that fixes are complete?

After fixing, it re-runs grep searches for old terms expecting zero results, then spot-checks critical files like system maps and workflow docs. Verification results are recorded in the final report with pass/fail status.