check-markdown-style

To check markdown formatting, the Skill applies a project's markdown style guide to target files, identifying deviations like improper heading hierarchy, trailing whitespace, and list formatting errors. It then outputs a clear report with violation locations and suggested fixes for immediate remediation.

A markdown style guide defines documentation formatting rules for consistency. This Skill enforces line length by applying Flowmark-aligned wrapping and a 100-character limit, while allowing specific exceptions, ensuring clean and readable documentation across README files and inline repository docs.

To fix heading hierarchy and blank line issues, run the Skill on your markdown file to validate structural correctness. It detects missing blank lines around blocks and improper heading levels, generating an actionable report with locations and suggested fixes to correct the formatting.

Yes, you can lint markdown table formatting and code blocks in README files. The Skill validates structural correctness across typical documentation tasks, detecting deviations from the style guide and providing remediation guidance to ensure clean, consistent documentation.

Markdown documentation often fails quality reviews because style violations slip through and degrade readability. This Skill detects deviations from the project's style guide, such as trailing whitespace and list formatting errors, generating an actionable violation report for immediate remediation.

The best way to enforce markdown lint rules is to apply a markdown style guide to target files within the repository. This Skill identifies violations across line-length, heading hierarchy, and table formatting, outputting an actionable list of deviations with suggested fixes for clean documentation.