docs-verify

To check documentation consistency, run an automated verification tool at your repository root to validate cross-references, detect missing files, and find duplicate definitions. This generates a concise report highlighting discrepancies and a health score.

Documentation cross-reference validation is the process of checking that internal links and canonical definitions point to existing, correct targets. You need it when maintaining large doc ecosystems to prevent outdated or conflicting information across modules.

You can find broken links and duplicate definitions by using file-based verification commands that read and search your project files. These commands identify missing target files and conflicting canonical references, then output a report with suggested fixes.

Yes, you can automate documentation quality checks by running a verification skill at your repository root. It uses bash, read, grep, and glob operations to perform file-based verification, making it suitable for large, multi-module project ecosystems.

The best way to maintain alignment is to run automated consistency checks that validate canonical definitions and cross-references against your project files. This ensures your root documentation stays synchronized with related module references.

Automated documentation verification relies on file-based checks using bash, read, grep, and glob, limiting it to validating static file references and definitions. It may not detect semantic inconsistencies or runtime-generated content.