Skill Detail
Map Python import graphs to explain coupling before refactors or package splits with pydeps
Generate Python module dependency graphs so refactors and package splits start from an actual import map instead of guesswork.
Code Quality & ReviewMulti-Framework
Code Quality & Review
Multi-Framework
Security Reviewed
⭐ 2.1k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill map-python-import-graphs-to-explain-coupling-before-refactors-or-package-splits-with-pydeps
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Python, Graphviz, a local Python codebase to analyze.
Install & setup
Install with pip install pydeps, then install Graphviz so the dot command is available on PATH.
Author
thebjorn
Publisher
Individual
Last updated
Apr 19, 2026
Quick brief
Use pydeps when an agent needs to inspect how Python modules depend on each other before a refactor, extraction, or architecture review. It is most useful when the real task is to surface import cycles, noisy coupling, or hidden dependency paths and hand back a graph or dependency report.
How it works
What this skill actually does
This is not just a package listing because the boundary is a specific analysis workflow: run dependency discovery against a target package, tune scope and noise, and produce a graph that explains coupling. That is a concrete operator task with a clear before-and-after artifact.