Debug & Review · LOCAL TOOL

Markdown QA

Review Markdown for heading-level jumps, duplicate generated heading IDs, and unresolved reference-style links before it is rendered.

Runs in this page
No API call

WORKSPACEINPUT → RESULT

Your input

LOCAL

Result

Run the tool to see a result.

Your result will appear here. Input is not saved.

Browser-side processingNothing is sent to a tool API.

WHY THIS TOOL EXISTS

A focused job, not a black box.

The report provides a table-of-contents preview and line references, so a writer can fix navigation issues without sending the document to a renderer.

How to use it

Paste Markdown source.
Run heading and reference checks.
Confirm generated heading anchors in your target renderer.

TRY A WORKING EXAMPLE

Start with known input.

Load this sample into the workspace, run the tool, and compare the result shown below.

Show sample input

{
  "markdown": "# Quick start\n\n## Install\n\nFollow the [setup guide][setup].\n\n### First run\n\n## Install\n\nThis repeated heading needs a distinct link target.\n\n[setup]: ./setup.md"
}

Expected sample result from the local tool

4 heading(s) · 1 finding(s).

Table of contents preview:
- [Quick start](#quick-start)
  - [Install](#install)
    - [First run](#first-run)
  - [Install](#install-1)

Findings:
Line 9: repeated heading anchor install-1.

Anchor generation approximates common GitHub-style behavior. Confirm final rendered anchors in the target Markdown renderer.

LIMITS AND INTERPRETATION

What the result cannot tell you.

Markdown dialects differ. Anchor generation approximates common GitHub-style behavior and does not fetch external links.

Inputs are processed in this page and are not written to local storage.