markdown-crossref-validator

Validate internal Markdown links, headings, and file targets across projects.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/prulloac/git-blame-vsc --skill markdown-crossref-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdown-crossref-validator
Source: https://github.com/prulloac/git-blame-vsc/tree/main/.agents/skills/markdown-crossref-validator
Command: npx skills add https://github.com/prulloac/git-blame-vsc --skill markdown-crossref-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate cross-references in Markdown documents by ensuring internal links, headings, and file targets exist and are accurate.

Core Features & Use Cases

  • Heading and anchor validation: Detect missing or mismatched anchors across single or multi-file Markdown projects.
  • Link integrity checks: Validate inline, reference-style, and HTML links to ensure they point to valid targets.
  • Cross-file validation: Resolve relative paths and cross-file references to confirm correctness and consistency in large documentation bases.

Quick Start

Install and run the validator against your Markdown project to get a report of broken references and suggested fixes.

Frequently Asked Questions about markdown-crossref-validator

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

FAQPage Schema
How do I validate markdown links and anchors across multiple documentation files?

To validate markdown links and anchors across multiple files, run the validator against your project to extract headings, resolve relative paths, and report broken internal references with actionable fix suggestions.

How does cross-reference validation work for inline and reference-style markdown links?

Cross-reference validation works by parsing markdown documents to extract headings, resolve anchors, and verify that inline, reference-style, and HTML links point to valid targets within the repository.

Can I check relative file paths and cross-file references in a large markdown documentation base?

Yes, you can check relative file paths and cross-file references by applying the validator to multi-file markdown projects, which resolves paths and confirms consistency across large documentation bases.

What is the best way to find missing heading anchors in a markdown project?

The best way to find missing heading anchors is to use a validation tool that extracts document headings and matches them against internal links, reporting mismatches and missing targets.

Does markdown link validation work with HTML links inside documentation files?

Markdown link validation works with HTML links by extracting and verifying them alongside inline and reference-style links to ensure they point to valid file targets and headings.

Why are my markdown internal links broken after renaming headings in my documentation?

Internal links break after renaming headings because the anchor references no longer match the new heading text, requiring validation to detect mismatches and suggest updated anchor links.