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 relationships", "find serializers", or when reading code and needing to understand what depends on a component before modifications.
Before you install
- Last update
- Files in folder
- 1
- Scripts
- No script files found
- SKILL.md size
- 2.8 KB (about 704 tokens of context each time it loads)
- License
- MIT
- Source on GitHub
- davila7/claude-code-templates
Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.
Install
npx skills add davila7/claude-code-templates@graph-queryRuns in a terminal with Node.js 18 or newer. Add -y to skip the prompts and -g to install for every project instead of this one.
Install for your agent
npx skills add davila7/claude-code-templates@graph-query --agent claude-code -y- Project install writes to
.claude/skills/graph-query- Global install writes to
~/.claude/skills/graph-query
Start a new session afterwards so the agent picks the skill up. In Claude Code you can also call it directly with /graph-query.
What it does
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. Core Behavior After reading any code file, query the graph to understand dependencies: Commands Query Command Description ---------------------- graph-describe.sh Describe a component or function graph-find-callers.sh Find all callers of a function graph-find-callees.sh Find all functions called by this function…
Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.
Categories
Related skills
- jira
davila7/claude-code-templates
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
- conversation-memory
davila7/claude-code-templates
Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.
- modal-serverless-gpu
davila7/claude-code-templates
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.
- crewai-multi-agent
davila7/claude-code-templates
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies for lean, fast execution.
- langchain
davila7/claude-code-templates
Framework for building LLM-powered applications with agents, chains, and RAG. Supports multiple providers (OpenAI, Anthropic, Google), 500+ integrations, ReAct agents, tool calling, memory management, and vector store retrieval. Use for building chatbots, question-answering systems, autonomous agents, or RAG applications. Best for rapid prototyping and production deployments.
- agent-memory-systems
davila7/claude-code-templates
Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm