mdcheck

Lint and fix Markdown files with markdownlint using Bun.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/raystyle/skills --skill mdcheck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mdcheck
Source: https://github.com/raystyle/skills/tree/main/skills/mdcheck
Command: npx skills add https://github.com/raystyle/skills --skill mdcheck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Markdown documentation often suffers from formatting inconsistencies across files and projects. mdcheck provides a consistent, automated way to lint and fix Markdown using markdownlint, reducing manual review time and improving readability.

Core Features & Use Cases

  • Lint and fix Markdown using markdownlint with a deterministic workflow.
  • Scan single files or entire projects to surface issues and apply safe fixes.
  • Use Case: ensure documentation across READMEs, CONTRIBUTING guides, and inline docs stays consistent.

Quick Start

Run the skill to lint and fix Markdown files across your project, then review and apply changes.

Frequently Asked Questions about mdcheck

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

FAQPage Schema
How do I lint and fix Markdown files across an entire project?

Linting and fixing Markdown across an entire project requires an automated tool that scans all files using markdownlint. It surfaces formatting inconsistencies and applies safe fixes automatically to improve readability.

Why does my Markdown documentation have inconsistent formatting across files?

Markdown documentation often suffers from formatting inconsistencies because it lacks enforced style rules. Linting with markdownlint provides a deterministic workflow to enforce style and correctness, reducing manual review time and improving readability.

Do I need Bun to run markdownlint for Markdown linting and fixing?

Yes, you need both markdownlint and Bun installed to execute the Markdown lint and fix workflows. These dependencies are required to scan files, apply configurable rules, and preview or write back fixes.

Can I preview Markdown fixes before writing them back to my files?

Yes, you can preview Markdown fixes before writing them back. The workflow supports lint-only and auto-fix modes, allowing you to scan single files or entire projects to surface issues and apply safe fixes selectively.

What's the best way to ensure READMEs and CONTRIBUTING guides follow consistent Markdown style?

The best way to ensure consistent Markdown style across READMEs and CONTRIBUTING guides is using markdownlint to enforce deterministic rules. This automates style and correctness checks, reducing manual review time and improving readability.

Does markdownlint support configurable rules for different project documentation?

Yes, markdownlint supports configurable rules to enforce style and correctness for different project documentation. You can scan single files or entire projects, applying these rules to surface issues and apply safe fixes automatically.