docs-lint

You can catch broken markdown links and invalid related-files paths by running automated docs validation that checks reference integrity across your documentation directory before committing changes. This prevents CI failures and broken user references.

The best way to detect stale tech-debt anchor references is to run an automated validator that parses documentation files and flags anchors that no longer resolve. This categorizes issues into actionable fix suggestions without manual error triage.

To identify architecture docs needing review, run stale doc detection which flags files whose last-reviewed date exceeds the 90-day threshold. It prioritizes outdated docs if their related file territory was modified in a PR.

Yes, you can automate documentation governance for PR reviews by running a pre-push hook validation or one-shot audit. It consumes validator JSON output to generate categorized, context-aware fix proposals for contributors.

Your CI check fails because modifying architecture files without updating related documentation triggers broken related-files paths and stale tech-debt anchors. Run a documentation linting check to catch these issues before pushing.

No, the docs validation process does not require manual error triage. It consumes validator JSON output and human-readable stale doc reports to generate categorized, actionable fix suggestions for each broken reference automatically.