graph-query

AI Maestro Code Graph Query

CRITICAL: AUTOMATIC BEHAVIOR - READ THIS FIRST

THIS IS NOT OPTIONAL. THIS IS YOUR DEFAULT BEHAVIOR.

Every time you use the Read tool on a code file, you MUST IMMEDIATELY query the graph to understand:

• What is this component/function?
• What depends on it? (callers, serializers, child classes)
• What does it depend on? (callees, parent classes, associations)

DO NOT:

• Wait for the user to ask you to query the graph
• Skip the graph query because "it seems simple"
• Assume you understand the impact without checking
• Make changes before understanding dependencies

ALWAYS:

• Query the graph IMMEDIATELY after reading any code file
• Query BEFORE making any modifications
• Query when you find files via search (grep/glob)
• Include graph findings in your analysis to the user

The Rule: Read File → Query Graph → Then Proceed

1. You read a file with Read tool
2. IMMEDIATELY run graph queries (describe, find-callers, find-serializers, etc.)
3. NOW you understand the full context
4. NOW you can analyze, modify, or discuss the code

Example - Reading a Model:

# After reading app/models/user.rb, IMMEDIATELY run:
graph-describe.sh User
graph-find-serializers.sh User
graph-find-associations.sh User

Example - Reading a Function:

# After reading a file with process_payment function, IMMEDIATELY run:
graph-find-callers.sh process_payment
graph-find-callees.sh process_payment

---

Available Commands

All commands auto-detect your agent ID from the tmux session. Just run them:

Query Commands

Command	Description
graph-describe.sh <name>	Describe a component or function
graph-find-callers.sh <function>	Find all functions that call this function
graph-find-callees.sh <function>	Find all functions called by this function
graph-find-related.sh <component>	Find related components (extends, includes, etc.)
graph-find-by-type.sh <type>	Find all components of a type (model, controller, etc.)
graph-find-serializers.sh <model>	Find serializers for a model
graph-find-associations.sh <model>	Find model associations (belongs_to, has_many)
graph-find-path.sh <from> <to>	Find call path between two functions