dependency-doctor

Diagnose dependency manifests for unpinned versions, backports, and conflicting pins.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Protremix/EvolvixOS --skill dependency-doctor-protremix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-doctor
Source: https://github.com/Protremix/EvolvixOS/tree/main/knowledge/skills/dependency-doctor
Command: npx skills add https://github.com/Protremix/EvolvixOS --skill dependency-doctor-protremix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Dependency manifests quietly accumulate footguns: packages that shadow the Python standard library, obsolete backports like dataclasses or enum34, unpinned dependencies that resolve differently on every machine, and duplicate or conflicting exact pins. This Skill inspects a single manifest and reports these surface-level problems with plain-language explanations and suggested fixes, without running a full resolver or vulnerability audit. ## Core Features & Use Cases - Offline manifest diagnosis: Parses requirements.txt, PEP 621 or Poetry pyproject.toml, and package.json using only the Python standard library, with no network calls by default. - Targeted checks: Detects standard-library shadowing pins, abandoned backports, unpinned dependencies, duplicate entries, and conflicting exact pins, each with severity, line number, and a suggested fix. - Opt-in PyPI yank check: With explicit --online approval, queries pypi.org to report exact Python pins whose releases are fully yanked. - Use Case: A developer's install fails mysteriously, so they run the doctor on requirements.txt and discover pathlib==1.0.1 shadowing the standard library plus two conflicting urllib3 pins, then apply the reviewed fixes. ## Quick Start Ask your agent to check my requirements.txt for dependency problems and explain any findings with suggested fixes.

Frequently Asked Questions about dependency-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check requirements.txt for dependency problems?▼

Run the dep_doctor.py script against your requirements.txt file to get a JSON report of findings. It flags standard-library shadowing pins, obsolete backports, unpinned dependencies, duplicates, and conflicting exact pins, each with a suggested fix.

How to detect conflicting dependency versions in a manifest?▼

The doctor groups entries by package and reports a high-severity conflict only when two exact pins disagree, such as urllib3==1.26.18 and urllib3==2.2.2. Compatible ranges split across lines are reported as duplicates to combine, not conflicts.

Does the dependency checker support pyproject.toml and package.json?▼

Yes, it parses PEP 621 and common Poetry dependency tables in pyproject.toml, plus dependencies, devDependencies, optionalDependencies, and peerDependencies in package.json. Python-specific checks like backports do not apply to package.json.

Does the dependency doctor work offline without network access?▼

Yes, the default run is fully offline and reads only the selected manifest using the Python standard library. Network access to pypi.org occurs only when you explicitly pass the --online flag to check for yanked releases.

What are the limitations of manifest-level dependency checking?▼

It does not resolve a full dependency graph, diagnose a failed pip or uv resolution, or query a vulnerability database. For CVE coverage, use pip-audit, npm audit, or your project's approved security scanner.