wasabeef/claude-code-cookbook/analyze-dependencies

/dependency-analysis [options]

# Analyze dependencies for entire project
/dependency-analysis
 
# Detect circular dependencies
/dependency-analysis --circular
 
# Detailed analysis of specific module
/dependency-analysis --focus src/core --depth 5

Dependency Analysis Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
📊 Metrics Overview
├─ Total modules: 42
├─ Average dependencies: 3.2
├─ Maximum dependency depth: 5
└─ Circular dependencies: 2 detected
 
⚠️  Architecture Violations
├─ [HIGH] src/domain/user.js → src/infra/database.js
│  └─ Domain layer directly depends on infrastructure layer
├─ [MED] src/api/auth.js ⟲ src/services/user.js
│  └─ Circular dependency detected
└─ [LOW] src/utils/helper.js → 12 modules
   └─ Excessive fan-out
 
✅ Recommended Actions
1. Introduce UserRepository interface
2. Redesign authentication service responsibilities
3. Split helper functions by functionality
 
📈 Dependency Graph
[Visual dependency diagram displayed in ASCII art]

# Automatic CI/CD checks
/dependency-analysis --circular --fail-on-violation
 
# Check against architecture rules
/dependency-analysis --rules .architecture-rules.yml
 
# See how dependencies changed
/dependency-analysis --compare HEAD~10

rules:
  - name: "Domain Independence"
    source: "src/domain/**"
    forbidden: ["src/infra/**", "src/api/**"]
 
  - name: "API Layer Dependencies"
    source: "src/api/**"
    allowed: ["src/domain/**", "src/application/**"]
    forbidden: ["src/infra/**"]
 
thresholds:
  max_dependencies: 8
  max_depth: 4
  coupling_threshold: 0.7
 
ignore:
  - "**/test/**"
  - "**/mocks/**"

# Check dependencies with package.json
cat package.json
/analyze-dependencies
"Find dependency issues in this project"
 
# Deep dive into a specific module
ls -la src/core/
/analyze-dependencies --focus src/core
"Check the core module's dependencies in detail"
 
# Compare design vs reality
cat docs/architecture.md
/analyze-dependencies --visual
"Does our implementation match the architecture docs?"