Query the code graph database to understand component relationships, dependencies, and change impact. Use when the user asks to "find callers", "check dependencies", "what uses this", "show relationships", "find serializers", or when reading code and needing to understand what depends on a component before modifications.
Query your codebase's dependency graph to understand component relationships, call chains, and the impact of changes before making modifications. Part of the AI Maestro suite.
Requires AI Maestro running locally with codebase indexed.
# Install graph tools
git clone https://github.com/23blocks-OS/ai-maestro-plugins.git
cd ai-maestro-plugins && ./install-graph-tools.sh
After reading any code file, query the graph to understand dependencies:
Read file -> Query graph -> Then proceed
| Command | Description |
|---|---|
graph-describe.sh <name> | Describe a component or function |
graph-find-callers.sh <fn> | Find all callers of a function |
graph-find-callees.sh <fn> | Find all functions called by this function |
graph-find-related.sh <component> | Find related components |
graph-find-by-type.sh <type> | Find all components of a type |
graph-find-serializers.sh <model> | Find serializers for a model |
graph-find-associations.sh <model> | Find model associations |
graph-find-path.sh <from> <to> | Find call path between functions |
| Command | Description |
|---|---|
graph-index-delta.sh [path] | Index or update the code graph |
Use with graph-find-by-type.sh: model, serializer, controller, service, job, concern, component, hook
# After reading a model file
graph-describe.sh User
graph-find-serializers.sh User
graph-find-associations.sh User
# Before modifying a function
graph-find-callers.sh process_payment
graph-find-callees.sh process_payment
# Find call chain between components
graph-find-path.sh handleRequest sendResponse
# Index your codebase
graph-index-delta.sh /path/to/project
Without checking the graph, you risk:
This skill is part of the AI Maestro platform, which provides 6 skills for AI agent orchestration: messaging, memory, docs, graph, planning, and agent management.