md-lint

Format and lint markdown files with Prettier and markdownlint-cli2.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/jimweller/davit-dataops-dotfiles --skill md-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: md-lint
Source: https://github.com/jimweller/davit-dataops-dotfiles/tree/main/claude-code/skills/md-lint
Command: npx skills add https://github.com/jimweller/davit-dataops-dotfiles --skill md-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures your markdown files are consistently formatted and adhere to linting standards, improving readability and maintainability across your documentation.

Core Features & Use Cases

  • Automated Formatting: Applies consistent styling to markdown files using Prettier.
  • Linting and Error Checking: Identifies and fixes common markdown errors and style violations using markdownlint-cli2.
  • Use Case: After writing a new README or updating documentation, run this skill to automatically format and check for any stylistic issues before committing.

Quick Start

Use the md-lint skill to format and lint all markdown files in the repository.

Frequently Asked Questions about md-lint

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

FAQPage Schema
How do I automatically format and lint markdown files in my repository?

You can automatically format and lint markdown files using Prettier and markdownlint-cli2 with auto-fix enabled, ensuring code style consistency and adherence to markdown best practices across all specified files.

What is the best way to fix markdown formatting and style violations before committing?

The best way to fix markdown formatting and style violations is to run an automated linting process with auto-fix enabled, which applies consistent styling and corrects common errors across your documentation.

Does this markdown linting tool support auto-fixing errors?

Yes, this markdown linting tool supports auto-fixing errors by running Prettier and markdownlint-cli2 with auto-fix enabled to automatically resolve common style violations and formatting issues.

Can I use Prettier and markdownlint-cli2 together to ensure markdown consistency?

Yes, you can use Prettier and markdownlint-cli2 together to apply consistent styling, identify errors, and enforce markdown best practices across all markdown files in your repository or specified paths.

Why should I run a markdown linter on my documentation?

You should run a markdown linter on your documentation to ensure consistent formatting and adherence to linting standards, which improves readability and maintainability across your markdown files.

How do I check for markdown style issues across multiple files?

You can check for markdown style issues across multiple files by running a linting skill that applies to all markdown files within a repository or specified file paths to identify and fix stylistic errors.