markdownlint

Configure Markdownlint in VSCode to lint Markdown files in-editor.

Updated Oct 23, 2025
One-click install
npx skills add https://github.com/elonfreedom/docs --skill markdownlint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdownlint
Source: https://github.com/elonfreedom/docs/tree/main/.github/skills/markdownlint
Command: npx skills add https://github.com/elonfreedom/docs --skill markdownlint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a lightweight workflow to configure and run Markdown linting inside Visual Studio Code, avoiding CLI tools for quick fixes.

Core Features & Use Cases

  • In-editor linting with the Markdownlint extension to catch common Markdown issues.
  • Workspace configuration and recommendations to standardize formatting across contributors.
  • Use Case: A writer or developer edits Markdown files and runs in-editor lint checks before submitting a PR.

Quick Start

Install the VSCode extension and enable in-workspace linting.

Frequently Asked Questions about markdownlint

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

FAQPage Schema
How do I lint Markdown files directly in VSCode before submitting a PR?

To lint Markdown in VSCode, you can automate in-editor checks using the Markdownlint extension to catch common formatting issues and get immediate feedback before submitting PRs.

What is the best way to standardize Markdown formatting across repository contributors?

Standardizing Markdown formatting across contributors is achieved by applying workspace configuration and a .markdownlint.json file to enforce repository-wide linting rules in VSCode.

Does in-editor Markdown linting require CLI tools to check documentation formatting?

In-editor Markdown linting does not require CLI tools; it provides a lightweight workflow by applying the Markdownlint extension inside VSCode to catch issues for quick fixes.

Can I configure custom Markdown linting rules for a single-repo documentation workstream?

You can configure custom Markdown linting rules for single-repo documentation workstreams by defining them in a .markdownlint.json file and applying optional workspace settings in VSCode.

What do I need to enable in-workspace Markdown linting for my documentation?

To enable in-workspace Markdown linting, you need VSCode and the Markdownlint extension installed, allowing you to apply repository-wide rules and receive immediate in-editor feedback.