doc-validator

To check for misplaced markdown files, scan your repository to validate that all .md files reside only within designated directories like docs/, skills/*/, or the root level, and output warnings for any non-compliant placements found.

Documentation sprawl is the uncontrolled spread of files across non-standard repository paths. Prevent it by validating markdown file locations and enforcing organizational standards that restrict .md files to designated directories such as docs/ or root.

Enforce repository structure standards by scanning for .md files outside of allowed directories like docs/ and skills/*/, then outputting warnings for non-compliant file placements to ensure a clean and organized repository structure.

Yes, you can validate markdown file locations before merging a feature branch by running a validation script that scans the entire repository and flags any new documentation files placed outside of the correct docs/ or skills/ subdirectories.

Valid locations for markdown files in a repository include designated directories such as docs/, skills/*/, and root-level documentation files. Files found outside these predefined paths are flagged as non-compliant.

Markdown files appear in wrong directories due to documentation sprawl, where organizational standards are not enforced. Scanning for .md files outside of designated directories like docs/ identifies these misplaced files and outputs warnings for correction.