← ClaudeAtlas

codebase-memorylisted

Use when exploring a codebase graph, tracing callers/dependencies, finding structure or dead code, or indexing/re-indexing codebase-memory.
SenjuWoo/Ultimate-AI-Starter-Bundle · ★ 7 · AI & Automation · score 78
Install: claude install-skill SenjuWoo/Ultimate-AI-Starter-Bundle
# Codebase Memory — Knowledge Graph Tools Use the graph for structural questions when its root and indexed source are current. Use text search for exact text and unsupported languages. Savings depend on the query and index coverage; do not infer a token bill from tool size. **Two halves to this skill.** Querying (below) is easy. **Indexing is where it goes wrong** — a careless `index_repository` on a Skyrim mod tree produces a 200,000-node graph of animation files that costs tokens on every query and answers nothing. Read "Indexing discipline" before your first `index_repository` on any repo. ## Quick Decision Matrix | Question | Tool call | |----------|----------| | Who calls X? | `trace_path(direction="inbound")` | | What does X call? | `trace_path(direction="outbound")` | | Full call context | `trace_path(direction="both")` | | Find by name pattern | `search_graph(name_pattern="...")` | | Dead code | `search_graph(max_degree=0, exclude_entry_points=true)` | | Cross-service edges | `query_graph` with Cypher | | Impact of local changes | `detect_changes()` | | Did the graph cover the source tree? | `check_index_coverage()` | | Risk-classified trace | `trace_path(risk_labels=true)` | | Text search | `search_code` or Grep | ## Exploration Workflow 1. `list_projects` — check if project is indexed and its recorded root still exists 2. `get_graph_schema` — understand node/edge types 3. `search_graph(label="Function", name_pattern=".*Pattern.*")` — find code 4. `get_code_snip