markdown-link-auditorlisted

# Markdown Link Auditor Verify that documentation references resolve without changing content unless the user explicitly requests fixes. ## Use this skill when - Markdown files, folders, or assets were added, moved, or renamed. - An index, README, guide, prompt, skill, workflow, or agent was changed. - A review needs evidence that local documentation references still work. ## Audit workflow 1. **Define scope.** Use the files and folders named by the user. If none are named, inspect the changed Markdown files and the nearest relevant index files. State the scope before reporting results. 2. **Reuse repository tooling.** Prefer an existing Markdown link checker or parser. Otherwise, tokenise Markdown carefully and ignore fenced code blocks and inline code unless the user asks to audit examples. 3. **Collect references.** Check inline links, reference-style links and definitions, images, and intentionally navigable autolinks. Preserve the displayed label and source location. 4. **Resolve local targets.** - Resolve relative paths from the source file's directory. - Split query or fragment identifiers from the path before checking the file. - Check the target exists with the repository's expected case. - For a fragment, match the rendered heading slug or an explicit HTML `id`/anchor. Apply the repository's slug rules when they are documented; otherwise use common GitHub-style slugging and note the assumption. - Treat `/` as the portable sepa