doc-validator

Preventing documentation sprawl involves scanning the repository for Markdown files outside standard directories like docs/ and skills/, then outputting warnings for non-compliant files to enforce organizational standards.

You validate Markdown file locations by scanning the repository for .md files and checking them against a predefined list of allowed directories and patterns to report non-compliant files.

Your Markdown files are flagged because they are located outside predefined standard directories such as docs/, skills/, or root-level documentation, violating organizational standards.

The best way to enforce documentation standards before merging is running a validation script that scans for misplaced .md files and outputs warnings for any files found in non-standard locations.

Yes, you can check repository structure by scanning for .md files outside predefined standard directories like docs/ and skills/, ensuring all new documentation files are placed correctly to prevent clutter.