dependency-doctor · patricio0312rev — Claude Code skill: dependency audit and upgrade plan
dependency-doctor scans your manifests, flags outdated and duplicated packages, known CVEs and risky version pairs, then hands back a report with a step-by-step upgrade plan.
MIT 261 installs ★ 64 updated 2026-01-12
npx skills add patricio0312rev/skills --skill dependency-doctor -a claude-codeWhat dependency-doctor does
Point the skill at a repo and it reads the manifests (package.json, requirements.txt, Cargo.toml, go.mod) against current stable releases. Then it hunts duplicates, known CVEs, libraries that have gone quiet for over two years, oversized bundles and peer dependency clashes.
Findings land in one report ordered by severity: security first, then performance, then upkeep. It carries the audit and update commands for npm, yarn, pnpm and pip, an upgrade sequence split into phases, and version ranges to write back into the manifest. Known bad package pairings and migration notes are covered in references/common-issues.md.
Framework majors get their own phase with a test run attached, since a breaking change is a different job from a patch. On Python projects the vulnerability pass runs through pip-audit or safety check, and without them that section of the report can't run.
What it helps with
- See which packages have fallen behind stable releases
- Collapse two copies of the same library into one version
- Pull CVE hits out of direct and transitive dependencies
- Split updates into phases so the build does not break in one go
- Pick version ranges that keep the problem from coming back
Example prompts for the agent
- Audit the dependencies in
package.jsonand tell me what's outdated, duplicated or vulnerable - Give me a phased upgrade plan for this pnpm workspace
- Check
Cargo.tomland suggest which versions to pin
How to install dependency-doctor
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill dependency-doctor -a claude-code2Manually: put the files in place
~/.claude/skills/dependency-doctor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dependency-doctor/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill dependency-doctor -a codex2Manually: put the files in place
.agents/skills/dependency-doctor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill dependency-doctor -a cursor2Manually: put the files in place
.cursor/skills/dependency-doctor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install patricio0312rev/skills foundation/dependency-doctor/SKILL.md2Manually: put the files in place
.github/skills/dependency-doctor/SKILL.md1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill dependency-doctor -a gemini-cli2Platform CLI
gemini skills install https://github.com/patricio0312rev/skills --path foundation/dependency-doctorManually: put the files in place
.devin/skills/dependency-doctor/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill dependency-doctor -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about dependency-doctor
How do I install dependency-doctor in Claude Code?
Run npx skills add patricio0312rev/skills --skill dependency-doctor -a claude-code. The skill file lands at ~/.claude/skills/dependency-doctor/SKILL.md.
What does dependency-doctor do?
It audits manifests for stale versions, duplicates, CVEs, heavy libraries and conflicting peer requirements, then writes a prioritised report with an upgrade path and pin suggestions.
Which package managers does it cover?
The report includes audit, outdated, dedupe and update commands for npm, yarn, pnpm and pip. The Python vulnerability check relies on pip-audit or safety check.
Source text
SKILL.md · MIT
--- name: dependency-doctor description: Audits project dependencies for outdated packages, duplicates, heavy/problematic libraries, security vulnerabilities, and risky version combinations. Generates prioritized reports with security, performance, and maintainability insights, upgrade paths, and safe pinning recommendations. Use when users request dependency audits, package updates, security checks, or dependency optimization. --- # Dependency Doctor Comprehensive dependency health analysis and upgrade planning. ## Core Workflow 1. **Scan manifests**: Analyze package.json, requirements.txt, Cargo.toml, go.mod, etc. 2. **Check versions**: Identify outdated packages against latest stable versions 3. **Detect issues**: Find duplicates, security vulnerabilities, deprecated packages, heavy bundles 4. **Assess risk**: Evaluate breaking changes and version compatibility 5. **Prioritize**: Rank issues by severity (security > performance > maintenance) 6. **Generate upgrade path**: Create safe, incremental update plan 7. **Recommend pins**: Suggest version constraints to avoid future issues ## Analysis Categories ### Security Issues (Critical) - Known CVEs in dependencies - Unmaintained packages (no updates >2 years) - Packages with security advisories - Transitive dependency vulnerabilities ### Outdated Packages (High) - Major versions behind (breaking changes) - Minor versions behind (new features) - Patch versions behind (bug fixes) ### Duplicate Dependencies (Medium) - Multiple versions of same package - Overlapping functionality (lodash + underscore) - Can be deduplicated ### Heavy Dependencies (Medium) - Large bundle sizes (>500KB) - Unnecessary peer dependencies - Better alternatives available ### Risky Combinations (Medium) - Known incompatible version pairs - Conflicting peer dependencies - Framework version mismatches ## Report Structure ````markdown # Dependency Audit Report ## 🔴 Critical Security Issues (2) - [email protected] → CVE-2021-3749 → Upgrade to 1.6.0+ - [email protected] → Prototype pollution → Upgrade to 4.17.21+ ## 🟡 High Priority Updates (5) - [email protected] → 18.2.0 (major, breaking changes) - [email protected] → 14.1.0 (major, new features) ## 🟢 Maintenance Updates (8) - [email protected] → 5.3.3 (patch improvements) ## 📦 Duplicates Found (3) - moment: 2.29.1, 2.30.0 → Deduplicate to 2.30.0 - @types/node: 18.0.0, 20.0.0 → Align to 20.0.0 ## 🏋️ Heavy Dependencies (2) - moment (232KB) → Consider date-fns (12KB) - lodash (full) → Consider lodash-es or specific imports ## Upgrade Path ### Phase 1: Security (Do First) ```bash npm update axios lodash npm audit fix ``` ```` ### Phase 2: Major Frameworks (Test Thoroughly) ```bash npm install react@18 react-dom@18 npm install next@14 # Run full test suite ``` ### Phase 3: Minor Updates (Low Risk) ```bash npm update ``` ## Safe Pin Recommendations ```json { "axios": "^1.6.0", "react": "^18.2.0", "typescript": "~5.3.0" } ``` ``` ## Package Manager Commands ### npm - Audit: `npm audit` - Outdated: `npm outdated` - Dedupe: `npm dedupe` - Update: `npm update [package]` ### yarn - Audit: `yarn audit` - Outdated: `yarn outdated` - Dedupe: `yarn dedupe` - Upgrade: `yarn upgrade [package]` ### pnpm - Audit: `pnpm audit` - Outdated: `pnpm outdated` - Dedupe: `pnpm dedupe` - Update: `pnpm update [package]` ### pip - Outdated: `pip list --outdated` - Update: `pip install --upgrade [package]` - Security: `pip-audit` or `safety check` ## Upgrade Best Practices 1. **Backup first**: Commit current state or create branch 2. **Read changelogs**: Check for breaking changes 3. **Update incrementally**: One major version at a time 4. **Test thoroughly**: Run full test suite after each update 5. **Check peer deps**: Ensure compatibility 6. **Lock files**: Commit updated lock files 7. **Monitor**: Watch for runtime issues after deployment ## Version Pinning Strategy - **Exact**: `1.2.3` - Only for problematic packages - **Patch**: `~1.2.3` - Safe updates (1.2.x) - **Minor**: `^1.2.3` - Most common (1.x.x) - **Range**: `>=1.2.3 <2.0.0` - Explicit bounds ## References See `references/common-issues.md` for known problematic package combinations and migration guides. ```
© patricio0312rev · MIT · patricio0312rev/skills
Similar skills
All skills for Security →dependency-doctor by other authors comes first.