markdown-lint-cleanup

Normalize Markdown headings, spacing, and code block language tags.

23|7|Updated Jan 23, 2026

Search Tags:#documentation #markdown #consistency #formatting #lint #style-guide

Ready to run

npx skills add https://github.com/peterbamuhigire/skills-web-dev --skill markdown-lint-cleanup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: markdown-lint-cleanup
Source: https://github.com/peterbamuhigire/skills-web-dev/tree/main/markdown-lint-cleanup
Command: npx skills add https://github.com/peterbamuhigire/skills-web-dev --skill markdown-lint-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Markdown lint warnings are a frequent source of inconsistency in documentation. This skill standardizes headings, spacing around lists and fences, and ensures language tags on fenced code blocks to produce clean, lint-free docs.

Core Features & Use Cases

Enforce proper headings by converting bold-only headings into structured heading levels (e.g., from Section Title to ## Section Title)
Ensure blank lines around lists and around fenced code blocks to improve readability and satisfy common lint rules
Enforce language tags on fenced code blocks to improve render accuracy and tooling support
Preserve content semantics while applying formatting normalization across large doc sets
Use case: apply to a project-wide Markdown repository to pass MD lint checks without content changes

Quick Start

Run a cleanup pass on the Markdown repository to fix lint warnings without altering content.

Frequently Asked Questions about markdown-lint-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix markdown lint warnings across a large documentation repository?▼

To fix markdown lint warnings across a large documentation repository, run a cleanup pass that normalizes headings, adds blank lines around lists and fences, and enforces language tags on fenced code blocks without altering content semantics.

What is the best way to convert bold-only text into structured markdown headings?▼

Converting bold-only text into structured markdown headings involves transforming lines like **Section Title** into proper heading levels such as ## Section Title to enforce style-guide compliance and improve documentation consistency.

Can I normalize formatting in markdown files with multiple authors without changing the content?▼

Yes, you can normalize formatting in markdown files with multiple authors without changing the content semantics, applying spacing and heading normalization to ensure readability while preserving the original text.

Why do my fenced code blocks fail markdown lint checks onboarding material?▼

Fenced code blocks fail markdown lint checks when they lack language tags. Adding language tags to fenced code blocks improves render accuracy and tooling support while satisfying common lint rules.

How do I ensure proper spacing around lists and fenced code blocks in markdown?▼

Ensuring proper spacing around lists and fenced code blocks in markdown requires inserting blank lines before and after these elements to improve readability and satisfy common markdown lint rules.

Does markdown formatting cleanup alter the semantics of my documentation?▼

Markdown formatting cleanup does not alter the semantics of your documentation, applying heading normalization and spacing adjustments to produce clean, lint-free docs while preserving the original content.