fix-markdown-lint

Fix Markdown linting errors in documentation files using markdownlint-cli2.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/tnez/docent --skill fix-markdown-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-markdown-lint
Source: https://github.com/tnez/docent/tree/main/.docent/skills/docent/fix-markdown-lint
Command: npx skills add https://github.com/tnez/docent --skill fix-markdown-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, markdownlint-cli2, and includes scripts (resource) components.

What problem does it solve?

Inconsistent Markdown formatting leads to messy documentation and CI/CD failures. This Skill automates the process of identifying and fixing Markdown linting errors using markdownlint-cli2, ensuring your documentation adheres to project standards and passes all automated checks, saving you manual correction time.

Core Features & Use Cases

  • Error Detection: Runs markdownlint-cli2 to identify all formatting issues in Markdown files.
  • Automatic Fixes: Automatically corrects ~95% of common linting errors (e.g., trailing spaces, blank lines around lists).
  • Manual Guidance: Provides clear instructions for manually fixing remaining errors like ordered list numbering.
  • Use Case: Your CI pipeline failed due to Markdown linting errors. Use this Skill to automatically fix most issues, get clear guidance on the few remaining manual fixes, and quickly get your documentation back to a passing state.

Quick Start

Fix all markdown linting errors in the documentation files.

Frequently Asked Questions about fix-markdown-lint

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

FAQPage Schema
How do I automatically fix Markdown linting errors in my documentation?

Markdown linting errors can be automatically fixed using markdownlint-cli2, which corrects ~95% of common issues like trailing spaces and blank lines around lists. Run `npm run lint:md` or `scripts/lint-markdown.sh` to auto-fix files across your repository, then commit the updated documentation.

Can I fix Markdown lint errors before my CI pipeline fails?

Yes. Run markdownlint-cli2 locally during development to catch and fix formatting issues before they reach CI. The Skill identifies all errors, auto-corrects most, and provides clear guidance for manual fixes, enabling quick verification and commits.

What Markdown linting errors can be fixed automatically?

markdownlint-cli2 automatically corrects ~95% of common Markdown formatting issues, including trailing spaces, blank lines around lists, and spacing inconsistencies. Remaining errors like ordered list numbering require manual correction with provided guidance.

Do I need Node.js and npm to fix Markdown linting errors?

Yes. The Skill requires Node.js and npm to run markdownlint-cli2. These dependencies enable the linting detection and auto-fix scripts that process all Markdown files in your repository.

How do I verify Markdown fixes are correct before committing?

After running the auto-fix script, review the updated Markdown files and error reports. The Skill outputs error lists and guidance for any remaining manual fixes, allowing you to verify corrections match project standards before committing changes.

Can this Skill fix Markdown errors across an entire repository?

Yes. The Skill applies markdownlint-cli2 to all repository Markdown content, handling both automatic fixes and manual corrections for common MD codes across CI lint runs, pre-merge checks, and local development workflows.