claude-md-link-check
claude-md-link-check audits CLAUDE.md files and .claude/rules/*.md files throughout a project to verify that all @-prefixed chain imports and markdown link targets point to existing files. The tool runs read-only, scanning relative path resolution and reporting broken links with their file locations and line numbers, making it useful for maintaining project documentation integrity without modifying any files.
git clone --depth 1 https://github.com/alirezarezvani/ClaudeForge /tmp/claude-md-link-check && cp -r /tmp/claude-md-link-check/skill/claude-md-link-check ~/.claude/skills/claude-md-link-checkSKILL.md
# 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. ``` 5. 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).
Create smart commit with quality checks and conventional format
Create pull request with proper validation
Initialize ClaudeForge CI/CD system
Create GitHub release with automated notes
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.
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.
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.
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.