claude-md-dependency-rescan
The claude-md-dependency-rescan skill automatically detects project dependencies from package.json, requirements.txt, pyproject.toml, go.mod, and Cargo.toml files, then compares them against the Tech Stack sections documented in CLAUDE.md files. Use this read-only tool to identify which dependencies have been added to manifests but not documented, removed from manifests but still documented, or have naming mismatches between documentation and actual project files.
git clone --depth 1 https://github.com/alirezarezvani/ClaudeForge /tmp/claude-md-dependency-rescan && cp -r /tmp/claude-md-dependency-rescan/skill/claude-md-dependency-rescan ~/.claude/skills/claude-md-dependency-rescanSKILL.md
# CLAUDE.md Dependency Rescan (forked, read-only) Optional explicit manifest: `$ARGUMENTS` (default: auto-detect all five manifest types). Run these steps in order. Do not modify any file. 1. **Detect manifests.** Look for `package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`, `Cargo.toml` at the repo root and one level deep (workspaces/monorepos). 2. **Extract declared dependencies** from each: - `package.json` → keys of `dependencies` and `devDependencies` (skip versions). - `requirements.txt` → first token of each non-comment line. - `pyproject.toml` → `[project.dependencies]` / `[tool.poetry.dependencies]` keys. - `go.mod` → module paths under `require (...)`. - `Cargo.toml` → keys under `[dependencies]` / `[dev-dependencies]`. 3. **Inventory documented deps** in every `CLAUDE.md` (and `.claude/rules/*.md`): grep for the Tech Stack / Dependencies sections and the lists under them. 4. **Compute three sets per file:** - `added`: in manifest but absent from this CLAUDE.md. - `removed`: documented in this CLAUDE.md but absent from manifest. - `renamed`: documented and present in manifest but spelled differently (`react-router` vs `react-router-dom`, `pg` vs `psycopg2`). 5. **Return** in this exact shape: ``` ## Dependency Rescan Manifests detected: <list> Total declared deps: <count> ### Per file #### <path-to-CLAUDE.md> - Added (in manifest, not documented): <list or "none"> - Removed (documented, not in manifest): <list or "none"> - Renamed / aliased: <list or "none"> ``` 6. If every documented set matches its manifest, return exactly `## Dependency Rescan\n\nAll documented deps match manifests. <M> files inspected.`. Do not pad. **Hard rule**: do not propose specific edits — just surface the diffs. `/sync-claude-md` decides whether to write them.
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.
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.
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.
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.