rules-doctor

To audit rules health and fix broken references, run a validation scan on the rules directory to detect missing files, verify cross-links, and produce a health report of integrity gaps.

Cross-reference validation for rule documents verifies that settings hooks reference existing scripts and documentation, ensuring alignment by checking that referenced rule files actually exist.

Detect missing domain files and stale mentions in anti-pattern indices by running coverage and consistency checks that ensure anti-patterns exist for domains and tech stacks align with documentation.

Yes, you can check settings.json hooks to verify they reference existing scripts by running a cross-reference validation scan that checks for broken references and missing files in the rules directory.

Broken reference detection matters for avoiding exfiltration risks because validating file references and enforcing consistent terminology prevents stale mentions that could expose misaligned security policies or data.