obsidian-doc-check

Obsidian markdown frontmatter and internal links are validated using automated Python scripts that check for mandatory YAML keys, correct formatting, and ensure [[...]] cross-references resolve correctly to maintain documentation integrity.

File naming conventions in Obsidian documentation are enforced by automated validation scripts that check consistency between filenames and document IDs, ensuring strict adherence to project-specific organizational standards before integration.

Yes, PyYAML is required as a dependency to parse and validate the YAML frontmatter within Obsidian markdown documents, enabling the automated checking of document structure and cross-references.

Broken links and missing metadata are caught by running an automated validation check across markdown documents in the docs directory, verifying link integrity and frontmatter compliance before committing changes to prevent integration issues.

Internal document links in Obsidian can be checked automatically without manual review by running validation scripts that verify [[...]] syntax resolves to valid targets, ensuring document discoverability and cross-reference integrity.

Markdown validation fails when document IDs and filenames mismatch because the convention rules enforce strict naming consistency, requiring filenames to exactly match their corresponding document IDs to pass automated checks.