Markdown Review Gate

The quality gate that runs before Markdown becomes HTML. A converter will happily render a document with three H1s, four dead links, an image with no alt text, and a 67-word sentence — the HTML validates and the page is still bad. This skill catches those defects while they are still cheap to fix, and fails the build when they are blocking.

Zero network calls, by design. Relative links and anchors resolve on disk; external URLs are inventoried and reported but never fetched. A gate that fails because someone else's server was slow is a gate engineers learn to ignore.

When to use this skill

• Before publishing a doc, guide, or article that will be converted to HTML
• Wiring a docs CI gate that must block a merge on real defects without blocking on style
• Auditing an inherited Markdown corpus to size the accessibility and link-rot backlog
• Enforcing house terminology across a docs set (front-end vs frontend, GitHub vs Github)
• Checking accessibility of source content against the WCAG criteria that survive conversion
• Calibrating prose to an audience — a runbook read at 3am needs a different band than an API reference