code-graph

# Code Graph Skill **Purpose:** Use the code graph (codebase-memory-mcp) for sub-millisecond symbol lookup, function search, dependency analysis, and blast radius detection. This replaces brute-force grep and file reading for code navigation. --- ## Core Principle **Graph first, file second.** Before reading files or grepping, query the code graph. Only read full files when you need to modify them or need context beyond what the graph provides. **Consider graph when planning.** When planning any change — feature, refactor, bug fix — start by querying the graph to understand scope, dependencies, and blast radius. This applies to thinking and planning phases, not just implementation. Grep is still the right tool for searching string literals, log messages, config values, and content that lives outside code structure. ``` ┌────────────────────────────────────────────────────────────────┐ │ GRAPH FIRST, FILE SECOND │ │ ─────────────────────────────────────────────────────────────│ │ The code graph indexes your entire codebase as a persistent │ │ knowledge graph. Claude queries it via MCP for instant │ │ symbol lookup, dependency chains, and blast radius — instead │ │ of reading hundreds of files. │ │ │ │ 14 MCP tools │ 64 languages │ sub-ms queries │ zero deps │ │ ~99% fewer tokens for navigation vs brute-force file re...