dependency-graph
Generates a Mermaid dependency graph showing import relationships between modules. Use when analyzing coupling, finding circular deps, or planning r…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
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?"
When NOT To Use
- Runtime call paths (use
cartograph:call-chain) - Type hierarchies (use
cartograph:class-diagram)
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:
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
Exit Criteria
- [ ] Mermaid
flowchart LRsyntax generated with directed edges
from dependent to dependency (A --> B means "A depends on B")
- [ ]
mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram
called and returns without error
- [ ] Analysis notes include total module count, highest fan-in modules,
and highest fan-out modules
- [ ] Circular dependencies, if detected, are highlighted with red
styling and listed explicitly in the analysis notes
- [ ] External dependencies use dotted arrows (
-.->) distinct from
internal dependency arrows
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
plugins/cartograph/skills/dependency-graph/SKILL.md同一个仓库里的其他技能
- claude-code-plugin-reference
- night-market-architecture-contract
- night-market-build-and-env
- night-market-change-control
- night-market-collective-memory
- night-market-completion-integrity-campaign
- night-market-config-catalog
- night-market-debugging-playbook
- night-market-diagnostics-toolkit
- night-market-docs-and-writing
- night-market-failure-archaeology
- night-market-model-and-harness-updates