Skip to content
cccskills
FreePublished on GitHub

claude-md-link-check

Verify every @path chain import and every markdown link inside every CLAUDE.md in this project resolves to an existing file. Read-only — returns broken links with file:line refs, never edits.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

CLAUDE.md Link Check (forked, read-only)

Optional path-glob: $ARGUMENTS (default . — entire tree).

Run these steps in order. Do not modify any file.

  1. Inventory. find <root> -name "CLAUDE.md" -type f -not -path "*/.git/*" -not -path "*/node_modules/*". Also include .claude/rules/*.md. Record paths.
  2. Extract candidates from each file:
    • Chain imports — lines matching ^@\S+. The literal after @ is a relative path.
    • Markdown links — [text](target) where target is not an HTTP(S) URL, not mailto:, not a bare anchor #section.
  3. Resolve each candidate relative to the file containing it (use Read on the parent file to confirm position, then test -e <resolved-path> or Glob).
    • For @../CLAUDE.md inside skill/CLAUDE.md, resolved path is CLAUDE.md.
    • For [Backend](backend/CLAUDE.md) inside the root, resolved path is backend/CLAUDE.md.
  4. Return the report in this exact shape:
## Link Check

Files inspected: <count>
References checked: <chain_imports> @-imports, <md_links> markdown links

### Broken
- <file>:<line> — `<original-target>` → does not resolve (expected `<absolute-path>`)
- ... (omit section if empty)

### Clean
<count> references resolved.
  1. If everything resolves, return exactly ## Link Check\n\nAll <N> references resolved across <M> files.. Do not pad.

Hard rule: never invent a fix. Report the broken target verbatim. Repair is the user's call (or /sync-claude-md's).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Re-detect this project's tech stack from package.json / requirements.txt / pyproject.toml / go.mod / Cargo.toml and diff it against the Tech Stack section of every CLAUDE.md. Read-only — returns added / removed / renamed dependencies, never edits.

The English summary is being prepared. Showing the original description.

alirezarezvani/ClaudeForge430Updated May 19, 2026

Audit every CLAUDE.md in this project for drift against the last week of git history. Flags sections that reference deleted files, renamed paths, or removed dependencies. Read-only — returns a punch list, never edits.

The English summary is being prepared. Showing the original description.

alirezarezvani/ClaudeForge430Updated May 19, 2026

Analyzes, generates, and enhances CLAUDE.md files for any project type using best practices, modular architecture support, and tech stack customization. Use when setting up new projects, improving existing CLAUDE.md files, or establishing AI-assisted development standards.

The English summary is being prepared. Showing the original description.

alirezarezvani/ClaudeForge430Updated May 19, 2026

Behavioral guardrails for LLM-assisted coding. Use when writing, reviewing, or refactoring code in any project to avoid overcomplication, keep changes surgical, surface assumptions early, and execute against verifiable success criteria.

The English summary is being prepared. Showing the original description.

alirezarezvani/ClaudeForge430Updated May 19, 2026

See all skills by alirezarezvani

Report a problem with this skill