OpenTrace

Analyzes dependencies and blast radius for code changes. Maps what depends on a given component and what it depends on. Use this agent to assess the impact of changes before making them. Use this agent when the user asks: - "What will this change break?" or "Is it safe to change X?" - "What uses X?" or "What depends on X?" - "What's the blast radius?" or "What's the impact of changing X?" - "What are the dependencies of X?" - "Show me upstream/downstream consumers" - "Which services will be affected if I modify X?" - Any question about change impact, risk assessment, or dependency mapping

Explores indexed code structure using the OpenTrace knowledge graph. Finds classes, functions, files, directories, services, modules, and their relationships. Use this agent to understand how code is organized, browse repo structure, trace dependencies, and discover connected components. Use this agent when the user asks: - "How does X work?" or "What does X do?" - "Where is X defined?" or "Find the X class/function/service/file" - "What calls X?" or "What does X call?" - "Show me the architecture" or "How is this organized?" - "What's in X?" or "Show me X" or "Look at X" or "List the files in X" - "What files/directories/services/classes are there?" - "Find X" or "What examples exist?" or "Where are the tests?" - "How are X and Y connected?" or "What's the relationship between X and Y?" - "Walk me through the codebase" or "Give me an overview" - Any question about repo structure, code organization, files, or component relationships

Answer a question about the codebase without making any changes. Use when: "how does X work", "what is X", "where is X", "explain X", "why does X"

Finds all usages, callers, and references to a specific component using the OpenTrace knowledge graph. Use this agent when the user asks: - "What calls X?" or "Who uses X?" - "Find all references to X" - "Where is X used?" or "Show me callers of X" - "What invokes this function/method/endpoint?" - Any question about finding usages, references, or callers of a component

Explains how a service, module, or major component works by walking the OpenTrace knowledge graph from the top down. Use this agent when the user asks: - "How does service X work?" or "Explain X to me" - "Give me an overview of X" or "Walk me through X" - "What does the X service/module do?" - "Help me understand X" or "I'm new to X" - Any request for a high-level explanation of a service or major component

Explore code structure, architecture, files, directories, and component relationships using the OpenTrace knowledge graph. Use this skill for ANY question about the codebase that the graph might answer — including browsing, searching, and understanding code organization. Triggers on: - Structure: "how does X work", "what calls X", "show me the architecture", "where is X defined" - Browsing: "what's in X", "show me X", "look at X", "list the files in X", "what directories are there" - Discovery: "find X", "what examples exist", "what services/classes/files are there" - Exploration: "walk me through X", "give me an overview", "help me understand X" - General: any question about repo structure, code organization, or component relationships

Index (or re-index) the current project into the OpenTrace knowledge graph. Use when: "index this repo", "re-index", "update the graph", "build the index"

Check for and install updates to the OpenTrace CLI (opentraceai). Use when: "update opentraceai", "update cli", "check for updates", "upgrade opentraceai", "new version"

General-purpose agent for answering ANY question about the codebase using the OpenTrace knowledge graph. This is the default agent to use when you're not sure which specialist to pick — it handles everything from file browsing to architecture exploration to dependency analysis. Use this agent when the user asks: - "What's in X?" or "Show me X" or "Look at X" - "Find X" or "Where is X?" or "What examples exist?" - "List the files/directories/services/classes" - "How does X work?" or "What does X do?" - "What calls X?" or "What depends on X?" - "Show me the architecture" or "Give me an overview" - "What's the repo structure?" or "What's in this directory?" - Any question about the codebase that might be answered by the indexed graph - When unsure whether to use @code-explorer, @dependency-analyzer, @find-usages, or @explain-service