dependency-doctor
Skill1 starsChanged 3 months agoMITView on GitHub
Diagnose dependency health across package managers (npm/pip/cargo/go): outdated packages, known vulnerabilities, unused dependencies, version conflicts, and license compliance issues, then produce a prioritized remediation plan. Use when managing, upgrading, or auditing project dependencies.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- milad-ahmd/agent-skillstheir own version, first seen Nov 1, 2026
- neeraj181-dot/ClaudeSkillstheir own version, first seen Aug 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- milad-ahmd/agent-skills★ 5same name
- neeraj181-dot/ClaudeSkills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- codebase-architectSkill
- deep-debuggerSkill
- documentation-engineerSkill
- performance-engineerSkill
- refactor-engineerSkill
- release-engineerSkill
- repo-resurrectionSkill
- security-auditorSkill
- test-engineerSkill
The file
Files
Dependency Doctor
Chẩn đoán sức khỏe dependencies bằng dữ liệu THẬT từ package manager, không đoán. Đầu ra: bảng vấn đề + plan fix ưu tiên + lệnh chạy được.
Quy trình (5 bước)
- Detect ecosystem: tìm lockfile/manifest (package-lock.json, requirements.txt, Cargo.toml, go.sum, pyproject.toml). Báo ecosystem phát hiện.
- Quét vấn đề (chạy script thật):
scripts/doctor.py <repo>chạy các check: outdated (so lockfile vs registry khi có network, hoặc heuristic version pattern khi không), vulnerable (so version với CVE database embeddedreferences/cves.json), unused (import analysis), conflicts, license.
- Phân loại severity: CRITICAL (CVE exploited), HIGH (CVE có fix), MEDIUM (outdated major), LOW (license info/unused).
- Remediation plan: thứ tự fix, lệnh upgrade cụ thể, cảnh báo breaking change, backup trước khi upgrade.
- Verify sau fix: chạy lại doctor, xác nhận vấn đề giảm; chạy test suite repo nếu có.
Nguyên tắc
- Mọi con số (số package, version, CVE) phải từ output của script thật, không ước lượng.
- Không tự động chạy
upgradekhông hỏi — luôn đưa plan trước, đợi xác nhận. - Lockfile là source of truth; không sửa file thủ công.
- Nếu không có network: chạy chế độ offline (check syntax, lockfile consistency, embedded CVE list), ghi rõ giới hạn.
Scripts
scripts/doctor.py <repo> [--ecosystem pip|npm|cargo|go] [--offline] [--output report.json]
References
- ECOSYSTEMS.md — đặc thù từng package manager
- CVE-LIMITATIONS.md — giới hạn database embedded
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.