lint-clean-markdown

Reduce Markdown lint errors by enforcing formatting rules during authoring.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/fabioc-aloha/Alex_Sandbox --skill lint-clean-markdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-clean-markdown
Source: https://github.com/fabioc-aloha/Alex_Sandbox/tree/main/.github/skills/lint-clean-markdown
Command: npx skills add https://github.com/fabioc-aloha/Alex_Sandbox --skill lint-clean-markdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you write Markdown that passes common lint rules on the first attempt, reducing iterative fixes.

Core Features & Use Cases

  • Lint-First Writing: Apply and internalize rules to produce lint-clean Markdown.
  • Rule References & Examples: Quick access to MD032, MD031, MD022, MD004, MD009, MD047 and related guidance.
  • Use Case: Draft README files for a project and ensure flawless formatting before review.

Quick Start

Use the lint-clean-markdown skill to validate and clean a Markdown document as you edit.

Frequently Asked Questions about lint-clean-markdown

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

FAQPage Schema
How do I write Markdown that passes lint rules on the first try?

To write Markdown that passes lint on the first try, apply specific formatting rules such as MD032, MD031, MD022, MD004, MD009, and MD047 during the drafting phase to ensure correct spacing, lists, and line endings.

What are common Markdown lint errors and how do I fix them?

Common Markdown lint errors involve blank line spacing around lists (MD032, MD031), heading blank lines (MD022), unordered list markers (MD004), trailing spaces (MD009), and missing end-of-file newlines (MD047).

How do I ensure my README formatting meets quality standards?

To ensure README formatting meets quality standards, apply lint-first writing guidance to validate spacing, lists, and document structure as you edit, reducing iterative fixes during review.

Can I use this to validate documentation formatting for wikis and developer notes?

Yes, you can validate documentation formatting for wikis and developer notes by applying these lint checks to any Markdown project, ensuring flawless formatting before the review process.

What is the best way to format Markdown without triggering trailing space or list errors?

The best way to format Markdown without triggering trailing space or list errors is to enforce lint rules like MD009 for trailing spaces and MD031, MD032 for proper blank line spacing around lists during authoring.