What is the primary requirement for this skill?

You must have markdownlint-cli installed globally via npm (npm install -g markdownlint-cli) for the skill to function.

What common errors does this skill detect?

It identifies issues such as incorrect heading increments, trailing spaces, multiple blank lines, bare URLs, and missing newlines at the end of files.

Can I skip errors if they seem minor?

No, this skill follows an 'Iron Law' approach where all errors must be resolved to ensure long-term documentation consistency and maintainability.

When does the validation process occur?

The skill is designed to run immediately after any Markdown file (.md) is created or edited, as well as during specific RPI phases like writing plans or design docs.

Markdown Validation

Name: Markdown Validation
Author: bostonaholic

bybostonaholic

•

Developer Tools

Validates and enforces consistent formatting for Markdown files using markdownlint to ensure error-free documentation.

About

The Markdown Validation skill integrates the markdownlint-cli directly into your Claude Code workflow to ensure all project documentation meets professional standards. By enforcing a zero-tolerance policy for linting violations, it helps developers maintain consistent heading hierarchies, correct spacing, and valid syntax across READMEs, research logs, and technical plans. This skill is part of the RPI framework, providing automated quality assurance that prevents documentation rot and formatting inconsistencies before they enter your version control system.

Key Features

Post-write verification hooks for immediate feedback after file modification
Automated validation using the industry-standard markdownlint-cli
2 GitHub stars
Real-time identification of common syntax errors like MD001 (headers) and MD009 (trailing spaces)
Strict 'Iron Law' workflow that ensures all errors are fixed before proceeding
Seamless integration with Research-Plan-Implement (RPI) framework documents

Use Cases

Validating research and planning documents during the RPI software engineering cycle
Automating documentation quality checks within the Claude Code terminal environment
Enforcing consistent formatting across project READMEs and technical documentation

About

Key Features

Post-write verification hooks for immediate feedback after file modification
Automated validation using the industry-standard markdownlint-cli
2 GitHub stars
Real-time identification of common syntax errors like MD001 (headers) and MD009 (trailing spaces)
Strict 'Iron Law' workflow that ensures all errors are fixed before proceeding
Seamless integration with Research-Plan-Implement (RPI) framework documents

Use Cases

Validating research and planning documents during the RPI software engineering cycle
Automating documentation quality checks within the Claude Code terminal environment
Enforcing consistent formatting across project READMEs and technical documentation