extract-dependencies
Analyze imports and identify all module dependencies. Use when mapping project structure.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install mvillmow-projectodyssey-extract-dependencies
Repository
Skill path: .claude/skills/tier-2/extract-dependencies
Analyze imports and identify all module dependencies. Use when mapping project structure.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: mvillmow.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install extract-dependencies into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/mvillmow/ProjectOdyssey before adding extract-dependencies to shared team environments
- Use extract-dependencies for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: extract-dependencies
description: "Analyze imports and identify all module dependencies. Use when mapping project structure."
mcp_fallback: none
category: analysis
tier: 2
---
# Extract Dependencies
Analyze import statements and identify all external and internal module dependencies in codebase.
## When to Use
- Understanding module coupling
- Planning dependency updates
- Identifying circular dependencies
- Generating dependency graphs
## Quick Reference
```bash
# Python dependency extraction
grep -r "^import\|^from" --include="*.py" . | sort | uniq
# Generate dependency graph
pipdeptree
# Check for circular dependencies
python3 -c "import ast; [print(f.name) for f in ast.walk(ast.parse(open('file.py').read())) if isinstance(f, ast.Import)]"
```
## Workflow
1. **Scan imports**: Extract all import statements from codebase
2. **Categorize dependencies**: Separate external, internal, standard library
3. **Map relationships**: Create graph of which modules import which
4. **Identify chains**: Trace dependency chains (A→B→C)
5. **Report analysis**: Document dependency structure and issues
## Output Format
Dependency analysis:
- External dependencies (with versions)
- Internal module dependencies
- Dependency graph (text or ASCII art)
- Circular dependencies (if found)
- Recommended import order
- Unnecessary or redundant dependencies
## References
- See `check-dependencies` skill for validation
- See `analyze-code-structure` skill for module organization
- See pixi.toml for declared project dependencies