Skip to content
Back to skills

Dependency Graph

ASecurity

Generates a Mermaid dependency graph showing import relationships between modules. Use when analyzing coupling, finding circular deps, or planning refactors.

  • 342 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 28, 2026
ai-agentsnoderefactoringgit

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add athola/claude-night-market --skill dependency-graph --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dependency Graph?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dependency Graph
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/athola-dependency-graph/badge)](https://www.skillsdirectory.com/skills/athola-dependency-graph)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dependency-graph
description: Generates a Mermaid dependency graph showing import relationships between modules. Use when analyzing coupling, finding circular deps, or planning refactors.
---

# Dependency Graph

Generate a Mermaid flowchart showing import and dependency
relationships between modules, packages, or plugins.

## When To Use

- Understanding what depends on what
- Finding circular dependencies
- Analyzing coupling between modules
- Planning refactoring by seeing dependency impact
- Answering "what breaks if I change this?"

## Workflow

### Step 1: Explore the Codebase

Dispatch the codebase explorer agent:

```
Agent(cartograph:codebase-explorer)
Prompt: Explore [scope] and return a structural model.
Focus on import statements and cross-module dependencies
for a dependency graph. Track both internal and external
imports.
```

### Step 2: Generate Mermaid Syntax

Transform the structural model into a Mermaid flowchart
with directed edges representing dependencies.

**Rules for dependency graphs**:

- Use `flowchart LR` (left-right) for dependency direction
- Each node is a module or package
- Edges point from dependent to dependency (A --> B means
  "A depends on B")
- Color-code by dependency type:
  - Default arrows for internal dependencies
  - Dotted arrows (`-.->`) for external/optional deps
  - Thick arrows (`==>`) for critical path dependencies
- Group into subgraphs by package/plugin
- If depth parameter given, limit transitive dependencies
- Highlight circular dependencies with red styling

**Example output**:

```mermaid
flowchart LR
    subgraph sanctum[Sanctum]
        commit[commit]
        pr_prep[pr_prep]
        workspace[workspace]
    end

    subgraph leyline[Leyline]
        git[git_platform]
        errors[error_patterns]
    end

    subgraph external[External]
        subprocess[subprocess]
        json[json]
    end

    commit --> git
    commit --> json
    pr_prep --> workspace
    pr_prep --> git
    workspace --> errors
    workspace -.-> subprocess
```

### Step 3: Render via MCP

Call the Mermaid Chart MCP to render:

```
mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram
  prompt: "Dependency graph of [scope]"
  mermaidCode: [generated syntax]
  diagramType: "flowchart"
  clientName: "claude-code"
```

If rendering fails, fix syntax and retry (max 2 retries).

### Step 4: Present Results

Show the rendered diagram with analysis notes:

- Total modules and dependency count
- Most-depended-on modules (high fan-in)
- Modules with most dependencies (high fan-out)
- Circular dependencies if any detected

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…