docs-links

Validates and auto-fixes broken internal markdown links and anchors across repository documentation.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/witwave-ai/witwave --skill docs-links-witwave-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-links
Source: https://github.com/witwave-ai/witwave/tree/main/.agents/self/kira/.claude/skills/docs-links
Command: npx skills add https://github.com/witwave-ai/witwave --skill docs-links-witwave-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation drifts out of sync as files are renamed and headings change, leaving broken internal links and dead anchors that frustrate readers. This Skill scans every markdown file in a repository, validates internal references, and automatically repairs unambiguous cases while logging ambiguous ones for human review. ## Core Features & Use Cases - Link and anchor validation: Checks inline links to other markdown files, same-file anchor links, and cross-document anchors using GitHub-flavored slug rules. - Git-history-aware auto-fixing: Traces file renames through git history and rewrites links when exactly one unambiguous new path is found. - Deferred findings logging: Records ambiguous broken references (missing anchors, unclear rename lineage) to a memory file for later triage instead of guessing. - Use Case: After a refactor that moves documentation files, run this Skill to detect link drift, automatically repair links whose targets were renamed, and receive a structured report of fixes applied and findings logged. ## Quick Start Ask the agent to check the documentation for broken internal links and fix the ones that can be resolved unambiguously.

Frequently Asked Questions about docs-links

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

FAQPage Schema
How do I find and fix broken internal links in markdown documentation?▼

Run this Skill to walk every markdown file, extract internal link targets, and validate them against the file tree and heading anchors. Unambiguous cases, such as a file renamed in git history, are fixed in place automatically.

How are markdown anchor links validated against headings?▼

Anchors are checked using GitHub-flavored slug rules: heading text is lowercased, spaces become hyphens, and punctuation other than hyphens and underscores is stripped. A reference is broken if the computed slug does not match any heading in the target file.

Does it check external https links in documentation?▼

No, external URL validation is explicitly out of scope because it requires network calls and is flaky. Only internal file links, same-file anchors, and cross-document anchors are validated.

What happens when a broken link cannot be fixed automatically?▼

Ambiguous cases, such as missing anchors or unclear rename lineage, are appended as one-line entries to a deferred-findings memory file for later human review. The Skill never guesses at ambiguous fixes.

Does the link checker commit the fixes it makes?▼

No, the Skill edits markdown files in place but never commits or pushes. Committing is owned by the orchestrator workflow that invokes it, such as the docs-scan pipeline.