doc-link-audit
SolidUse before publishing documentation, merging a docs PR, or reporting a Markdown-heavy repo's navigation as complete — when you want ground-truth confirmation that internal links, heading anchors, and directory links resolve, without opening every file yourself.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- Rtur2003
- Repository
- Rtur2003/Claude-Code-Promts-Skills
- Created
- 8 months ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
docs-checker
Audit context files (CLAUDE.md, .claude/ tree, READMEs, docs) for broken references and verifiably stale content. Runs a deterministic offline link/path checker first, then a bounded semantic review where every finding must cite evidence. Reports findings; fixes only on request.
md-audit
Audit human-facing markdown (README, CONTRIBUTING, SECURITY, docs/**, package READMEs) for claims the repo no longer satisfies — commands that fail, flags that don't exist, described behaviour the code dropped. Runs after scripts/audit-markdown.mjs has settled the mechanical findings. Use weekly from the docs-audit routine, or after a refactor that moved user-facing surfaces.
link-auditor
Checks every link in a markdown file and reports the dead ones with the line each sits on. Entry is the `links:` prefix and nothing else: "links: <path>" checks one file, "links:" alone checks the working directory. Not for rewriting links, and not for anything that is not markdown. Demonstration input for skill_audit's [D] preflight — the angle-bracket placeholder above is the only thing wrong with this file.