dependency-doctor

A skill in Shubhamsaboo/awesome-llm-apps · 145,077 stars on GitHub

Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-library shadowing pins, abandoned backports, unpinned dependencies, and obvious intra-manifest conflicts, plus opt-in PyPI yanked releases. Use when the user asks to check a manifest for dependency problems, asks why dependencies won't install or whether anything is wrong with their dependencies, wants a dependency autopsy, or suspects dependency manifest rot. Runs offline by default as a local tool for the user's own project, not repository CI.

Security grade of this SKILL.md: SAFE · how we grade

How to install dependency-doctor

npx skills add Shubhamsaboo/awesome-llm-apps --skill dependency-doctor -a claude-code

The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.

What the SKILL.md says

Inspect one dependency manifest on the user's machine for direct, surface-level footguns. Explain each finding in plain language, then offer a small, reviewable fix. This does not diagnose a failed pip or uv resolution. This is a local developer tool for a project the user chooses. It is not a repository-wide lint rule, a CI gate, or a proposal to enforce dependency policy across unrelated apps. The user asks to check, audit, diagnose, or autopsy a dependency manifest. The user wants to rule out direct-manifest issues before deeper install debugging. The user suspects stale pins, backports, duplicate entries, or dependency rot. The user asks whether anything looks wrong with their dependencies. Installing the current dependencies without diagnosing them. Upgrading every package or adding a new package. A full vulnerability audit.

Other skills in Shubhamsaboo/awesome-llm-apps

  • advisor-orchestrator-worker Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen compe…
  • commit-archaeologist Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion f…
  • first-reader Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read pr…
  • project-graveyard Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer…
  • scope-creep-detector Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dep…
  • thinking-out-loud A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing unt…