docs-validating-links

To check for broken markdown links, scan all markdown files in directories like docs/ to validate internal relative paths, enforce .md extensions, and verify external URL HTTP status accessibility. This detects formatting errors and inaccessible resources before merging documentation changes.

External URL verification validates HTTP and HTTPS accessibility for links inside markdown files. It applies cached validation results to minimize redundant network requests, ensuring external resources remain accessible and documentation credibility stays intact.

Detect unsupported wiki-link syntax by scanning markdown files for formatting compliance. Validation workflows check internal documentation paths for correct relative links and required .md extensions, flagging any wiki-link syntax that degrades navigation.

Yes, you can validate internal documentation paths across docs/, repo-governance/, and plans/ directories. The validation checks link existence, enforces .md extensions for documentation files, and ensures relative paths resolve correctly across multi-file documentation sets.

Broken link detection matters because broken markdown links degrade documentation usability and user navigation. Locating malformed links manually in large repositories is difficult, so automated validation ensures formatting compliance and external accessibility before shipping.

The best way to scan markdown files before merging is to run a validation checker across directories like docs/ and plans/. This verifies internal path existence, enforces .md extensions, checks external HTTP status, and stores cached validation results.