solo-residual-audit

Detect broken relative links and incorrect parent-directory depth across all Markdown files in a workspace.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-residual-audit-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-residual-audit
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v1.2.0/skills/solo-residual-audit
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-residual-audit-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? As Markdown documentation accumulates, relative links silently break and parent-directory references (../) drift out of sync with actual folder depth. This Skill audits the entire workspace in one pass and records the findings in a report, complementing single-file link checks that run after each edit. ## Core Features & Use Cases - Broken Link Detection: Scans every .md file for relative Markdown links pointing to non-existent local paths, skipping external URLs, anchors, and archived directories. - Depth-Up Validation: Verifies that ../ sequences in placeholder files like _index.md match the file's actual depth from the workspace root. - Report Generation: Writes a dated audit report to docs/00_관리/ when available, otherwise prints a console summary with file and line numbers. - Use Case: Before a release or during a monthly maintenance pass, run a full workspace scan to confirm zero broken links and catch depth mismatches introduced by moved or renamed folders. ## Quick Start Ask the assistant to run a full workspace link integrity audit and report all broken relative links in the Markdown files.

Frequently Asked Questions about solo-residual-audit

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

FAQPage Schema
How do I find broken links in Markdown files?▼

Scan all .md files with a regex matching Markdown link syntax, resolve each relative path against the file's directory, and check whether the target exists on disk. External URLs, mailto links, and anchors are excluded from validation.

How to check relative path depth in Markdown documentation?▼

Compare the number of ../ segments in placeholder files like _index.md against the file's actual depth from the workspace root. Mismatches indicate copy-paste errors where a fixed depth was applied regardless of folder location.

Does the link checker scan archived or backup files?▼

No, directories containing _archive or archive in their path and files with .bak. in the name are skipped during the walk. This prevents stale archived content from polluting the audit results.

Can this tool fix broken Markdown links automatically?▼

No, it only detects and reports broken links with file and line references. Fixing links is left to user judgment as a separate task, since the correct target often requires human context.

Where is the link audit report saved?▼

The report is written to docs/00_관리/ with a dated filename like residual-audit-20240115.md when that directory exists. If the directory is missing, only a console summary of broken links is printed.