cross-reference-validation

Cross-reference validation automatically detects broken internal links, invalid file paths, and outdated line-number references in your documentation, then suggests fixes. It scans Markdown files and verifies that all file paths, links, and code examples still point to valid locations in your codebase.

Yes. Code example verification ensures that code blocks with imports correctly reference existing exports in your codebase. This catches outdated imports and missing functions before they frustrate users.

Git-aware validation detects file moves through Git history and automatically suggests updates to outdated references. Before merging large refactors, run validation to ensure all documentation points to renamed or relocated files.

Yes. Cross-reference validation applies to documentation repositories and feature branches where code evolves. It handles relative and absolute link verification, file:line validation, and code block validation across docs and source trees.

The Skill provides auto-fix suggestions and supports optional auto-update workflows, allowing you to automatically correct broken links and references rather than fixing them manually.

As code evolves, documentation often falls behind, creating link rot that frustrates developers and wastes troubleshooting time. Automated validation catches these issues early and keeps your documentation reliable and accurate.