AI Maestro Code Graph Query

SkillDatabases & data

Graph-query is a skill that lets an AI agent query the code graph database to understand component relationships, dependencies, and change impact. When reading code, it answers questions like what calls a component or what depends on it, so the agent can trace how changes ripple through the codebase. It is a graph claude skill aimed at dependency and impact analysis.

Available today. Use it from your connected AI after setup.

Have the code graph database available and populated for the codebase.

Then ask your AI: use the AI Maestro Code Graph Query skill

What your AI can do with it

  • Find callers of a given component
  • Check dependencies of a component
  • Show relationships between components
  • Find serializers in the codebase
  • Assess change impact before modifying a component

Getting started

  1. Have the code graph database available and populated for the codebase.
  2. Add the graph-query skill to the agent's available skills.
  3. Ask the agent questions such as "find callers" or "check dependencies" and it will query the graph.

What this skill tells your AI

The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/ai-maestro/graph-query/SKILL.md and read by ahel’s review.

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.

Prerequisites

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

Core Behavior

After reading any code file, query the graph to understand dependencies:

Read file -> Query graph -> Then proceed

Commands

Query

CommandDescription
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

Index

CommandDescription
graph-index-delta.sh [path]Index or update the code graph

Component Types

Use with graph-find-by-type.sh: model, serializer, controller, service, job, concern, component, hook

Usage Examples

# 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

Why Query Before Modifying

Without checking the graph, you risk:

  • Breaking callers when changing a function signature
  • Missing serializers that need updating with a model change
  • Overlooking child classes that inherit your modifications

Full AI Maestro Experience

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.

Signals

GitHub stars
32k
Forks
4k
Last commit
Sep 2026

Questions

When should the agent use this skill?
When the user asks to "find callers", "check dependencies", "what uses this", "show relationships", or "find serializers", or when reading code and needing to understand what depends on a component.
What does it query?
The code graph database, which holds component relationships and dependencies for the codebase.
Can it show change impact?
Yes. It is designed to help understand change impact by showing which parts of the codebase depend on or call a component.
Advanced
Item type
skill
Key
graph-query-davila7
Source
github.com/davila7/claude-code-templates