fixing-broken-links

Crawl links in files and projects and repair broken references.

672|104|Updated Apr 10, 2026

Search Tags:#documentation #markdown #validation #repository #links #http

Ready to run

npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill fixing-broken-links

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fixing-broken-links
Source: https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/fixing-broken-links
Command: npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill fixing-broken-links

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of hunting through documentation and project files for dead links, letting you quickly identify and repair broken references before they confuse readers or break builds.

Core Features & Use Cases

Link Discovery: Scans Markdown links, bare URLs, HTML href and src attributes, reference-style definitions, and local relative paths.
Link Validation: Checks external URLs with HTTP requests and verifies local file paths on disk.
Repair Workflow: Updates moved links, removes unrecoverable references, and records unreachable targets for follow-up.
Use Case: Use this Skill when you want to clean up a repository README, documentation set, or knowledge base after content has moved or files have been renamed.

Quick Start

Use the fixing-broken-links skill to scan the target file or repository, validate every link, and fix or remove any broken references it finds.

Frequently Asked Questions about fixing-broken-links

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

FAQPage Schema

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

Broken links in markdown files are identified by scanning reference-style links and bare URLs, verifying HTTP responses with curl, and checking local filesystem existence. The tool then updates moved links, removes unrecoverable references, and reports unreachable targets.

What's the best way to validate local relative paths and external URLs in a repository?▼

The best way to validate repository links is to check external URLs with HTTP requests and verify local relative paths on disk. This confirms whether your markdown and HTML files contain reachable targets before updating or removing broken references.

Does this link validation approach work with HTML href and src attributes?▼

Yes, link validation works with HTML href and src attributes alongside markdown links and reference-style definitions. It checks external URLs via HTTP requests and verifies local file paths on disk to ensure all project references are reachable.

How do I clean up a repository README after files have been renamed?▼

To clean up a README after renaming files, scan the repository to validate local relative paths and external URLs. The validation process identifies broken references, updates moved links, and removes unrecoverable entries automatically.

What happens to unrecoverable dead links during the repair workflow?▼

During the repair workflow, unrecoverable dead links are removed from the files, and their unreachable targets are recorded for follow-up. This ensures documentation remains clean while providing a report of what was deleted.