markdown-formatter

Lint and format Markdown files to enforce consistent styling rules.

Updated Mar 24, 2026

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

Ready to run

npx skills add https://github.com/balamuru/antigravity-dev-skills --skill markdown-formatter-balamuru

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: markdown-formatter
Source: https://github.com/balamuru/antigravity-dev-skills/tree/main/.agents/skills/markdown-formatter
Command: npx skills add https://github.com/balamuru/antigravity-dev-skills --skill markdown-formatter-balamuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Markdown documents often suffer from inconsistent styling, readability issues, and drift across large teams. This skill automatically enforces a strict, reproducible formatting standard without altering content semantics.

Core Features & Use Cases

Enforces header spacing: ensures a blank line before and after headers and reserves H1 for the document title.
Normalizes lists: uses hyphens for unordered lists, requires a blank line before lists, and maintains consistent indentation for nested items.
Standardizes blocks: enforces code fences with language tags and cleans up emphasis and trailing spaces.
Use case: Maintains a uniform style across a large documentation repo with multiple authors.

Quick Start

Format target Markdown files in your project to adhere to the defined style rules using this formatter.

Frequently Asked Questions about markdown-formatter

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

FAQPage Schema

How do I enforce consistent Markdown formatting across a multi-repo documentation project?▼

You can enforce consistent Markdown formatting across multi-repo docs by using a linter that imposes header spacing, list hygiene, code fence usage, and table padding to maintain uniform style without altering content semantics.

What does consistent Markdown styling do to header spacing and list hygiene?▼

Consistent Markdown styling ensures a blank line before and after headers while reserving H1 for the document title. It normalizes lists by using hyphens, requiring preceding blank lines, and maintaining consistent nested indentation.

How do I standardize code fences and emphasis conventions in documentation files?▼

To standardize code fences and emphasis conventions in documentation files, apply a formatter that enforces code fences with language tags and cleans up emphasis formatting as well as trailing spaces to ensure readability.

Can I use a Markdown linter for team-wide documentation without changing the content semantics?▼

Yes, you can use a Markdown linter for team-wide documentation projects to automatically enforce a strict, reproducible formatting standard. The process normalizes styling and structural drift while preserving the original content semantics.

When should I use an automated Markdown formatter over manual style guide enforcement?▼

You should use an automated Markdown formatter over manual style guide enforcement when managing large documentation repositories with multiple authors, preventing formatting drift and ensuring uniform style reproducibility across files.