check-markdown

Fix markdown formatting by detecting and correcting list normalization, heading validation, and platform-specific admonitions for Docusaurus or VitePress. The workflow enumerates issues and prompts for confirmation before applying batch fixes.

Normalizing markdown admonitions involves platform detection and mapping callout syntax for VitePress, Docusaurus, and MkDocs. This ensures documentation remains render-safe and preserves platform-specific syntax like MDX and Vue components.

Yes, this markdown linter supports GitHub Flavored Markdown as a fallback and explicitly processes both .md and .mdx files. It validates heading rules, code fence language tags, and image alt text while preserving frontmatter and platform-specific components.

Enforce single H1 headings and consistent list markers by applying markdown linting rules to your documentation files. The workflow checks heading spacing, normalizes list markers, and corrects nested list indentation before applying non-destructive batch fixes.

Yes, you can review markdown formatting issues before they are fixed because the workflow enumerates all detected problems and asks for user confirmation. It then applies non-destructive, semantics-preserving batch fixes only after you approve.

Markdown tables and code fences render incorrectly in MkDocs when table separator spacing is inconsistent or code fence language tags are missing. Detecting these formatting issues and applying guided corrections ensures your documentation renders safely.