← ClaudeAtlas

aio-maplisted

Trace dependencies, call graphs, and blast radius for a file/function/module via GitNexus + LSP. Step 2 of the codeflow discover → map → plan trio (after aio-discover, before aio-plan).
aiocean/claude-plugins · ★ 3 · AI & Automation · score 63
Install: claude install-skill aiocean/claude-plugins
# Map — Structural Analysis ## Environment - GitNexus: !`npx gitnexus status 2>/dev/null && echo "AVAILABLE" || echo "NOT INSTALLED"` Build a dependency and symbol map for files identified by `/discover`. Uses GitNexus for overview, LSP for precision. ## Prerequisites - GitNexus indexed (`npx gitnexus analyze`) — verify with `npx gitnexus status` - LSP servers running (TypeScript/Rust) ## Workflow ### Step 1: Symbol inventory (GitNexus) — run in parallel For each relevant file from discovery, use the GitNexus MCP `context` tool: ``` context(file) ``` Fast overview of symbols and dependencies without reading the full file. ### Step 2: File dependencies (GitNexus) — run in parallel ``` context(file) → imports and dependents for the file impact(file) → what does changing this file affect? ``` **Note:** GitNexus tracks TS imports well. For Rust modules, fall back to LSP. ### Step 3: Precise references (LSP) For key functions that will be modified: ``` lsp_find_references(file, line, character) → all call sites lsp_goto_definition(file, line, character) → where defined lsp_hover(file, line, character) → type info ``` LSP is authoritative — always trust LSP over GitNexus for caller/callee data. ### Step 4: Output structural map ``` ## Map: [feature area] ### File: `path/file.ts` (N functions) **Key functions:** fn1, fn2, fn3 **Imports:** file-a.ts, file-b.ts **Imported by:** file-c.tsx, file-d.tsx **References:** - `fn1` called from: file-c.tsx:42