AI Maestro Code Graph Query

Queries code graph to determine component relationships and change impact.

744|94|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/23blocks-OS/ai-maestro --skill ai-maestro-code-graph-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: AI Maestro Code Graph Query
Source: https://github.com/23blocks-OS/ai-maestro/tree/main/skills/graph-query
Command: npx skills add https://github.com/23blocks-OS/ai-maestro --skill ai-maestro-code-graph-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

PROACTIVELY query the code graph database to understand relationships and impact of changes. Use this skill WHEN READING any file to understand context, when searching for files, when exploring the codebase, or when you need to understand what depends on a component. This is your primary tool for understanding code structure and avoiding breaking changes.

Core Features & Use Cases

  • Immediate graph queries: After reading a code file, 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)
  • Impact analysis: Surface callers, serializers, and associations to prevent breaking changes.
  • Use Case: While exploring a module, run graph queries to map relationships before editing the code.

Quick Start

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

Frequently Asked Questions about AI Maestro Code Graph Query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I understand what parts of my codebase depend on a component I'm about to change?

Query the code graph to find callers, serializers, and dependencies immediately after reading a file. Run graph-find-callers.sh to surface all code that depends on your component, preventing breaking changes before you modify it.

What's the best way to analyze code relationships and dependencies before making edits?

Use graph queries to map relationships: graph-describe.sh identifies the component, graph-find-callers.sh and graph-find-serializers.sh reveal dependents, and graph-find-callees.sh shows what it depends on. Run these immediately after reading code to understand impact.

Can I determine which serializers and child classes reference a specific model or function?

Yes. Graph queries return serializers and associations that reference your component. Run graph-find-serializers.sh and graph-find-associations.sh to surface all references before modification, ensuring you catch indirect dependencies.

How do I keep the code graph updated as my codebase changes?

The Skill supports delta indexing to maintain graph accuracy after edits. Rerun graph queries after modifications to refresh relationships and validate that changes propagated correctly through callers and dependencies.

What information does a code graph query provide about a component's relationships?

Graph queries return what a component is, what calls it, what it calls, which serializers reference it, and related associations. This reveals the full dependency tree and impact radius needed to avoid unintended side effects.