Markdown Quality

Treat Markdown as a document format inside a real publishing system, not as plain text with a universal style template. A good change preserves meaning, works in the document's renderer, helps the intended reader, and avoids noisy format churn.

Choose the right scope

• Review when the user wants findings or recommendations without edits.
• Improve when existing Markdown should become clearer, more consistent, accessible, accurate, or maintainable.
• Create when a new document is needed and its role and source material are known.
• Repo-wide when the request covers multiple Markdown files or asks for consistency across the repository. Build a role map first; do not apply one template to every file.

Choose this skill or readme-first