Graph Query
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 relatio...
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.
Install
Quick install
npx skills add https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/ai-maestro/graph-querynpx skills add davila7/claude-code-templates --skill graph-query --agent claude-codenpx skills add davila7/claude-code-templates --skill graph-query --agent cursornpx skills add davila7/claude-code-templates --skill graph-query --agent codexnpx skills add davila7/claude-code-templates --skill graph-query --agent opencodenpx skills add davila7/claude-code-templates --skill graph-query --agent github-copilotnpx skills add davila7/claude-code-templates --skill graph-query --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add davila7/claude-code-templates --skill graph-queryManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/davila7/claude-code-templates.gitcp -r claude-code-templates/cli-tool/components/skills/ai-maestro/graph-query ~/.claude/skills/AI Maestro Code Graph Query
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
| 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 |
Index
| Command | Description | |---------|-------------| |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.
SKILL.md source
--- name: graph-query description: 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 relatio... --- # AI Maestro Code Graph Query 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](https://github.com/23blocks-OS/ai-maestro) suite. ## Prerequisites Requires [AI Maestro](https://github.com/23blocks-OS/ai-maestro) running locally with codebase indexed. ```bash # 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 | 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 | ### Index | Command | Description | |---------|-------------| | `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 ```bash # 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](https://github.com/23blocks-OS/ai-maestro) platform, which provides **6 skills** for AI agent orchestration: messaging, memory, docs, graph, planning, and agent management.
Related skills 6
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
secure-linux-web-hosting
Use when setting up, hardening, or reviewing a cloud server for self-hosting, including DNS, SSH, firewalls, Nginx, static-site hosting, reverse-proxying an app, HTTPS with Let's Encrypt or ACME clients, safe HTTP-to-HTTPS redirects, or optional post-launch network tuning such as BBR.
readme-i18n
Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
lark-shared
Use when first setting up lark-cli, running auth login, switching user/bot identity (--as), handling permission denied or scope errors, needing to update lark-cli, or seeing _notice in JSON output.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
paper-context-resolver
Optional RigorPilot helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacin...