Query a codebase knowledge graph for call traces, dependencies, and structural analysis.
npx skills add https://github.com/avdi/purse --skill codebase-memory-avdi
Please help me install this Agent Skill. Skill: codebase-memory Source: https://github.com/avdi/purse/tree/main/home/dot_agents/skills/codebase-memory Command: npx skills add https://github.com/avdi/purse --skill codebase-memory-avdi
trace_path, including risk-classified traces. - Structural Search: Find functions by name pattern, detect dead code via degree filters, and identify high fan-in/fan-out refactor candidates with search_graph. - Cross-Service Analysis: Run raw Cypher queries with query_graph to inspect HTTP_CALLS, ASYNC_CALLS, and other edge types across services. - Use Case: Before refactoring a shared handler, run search_graph to find its exact name, then trace_path(direction="both", depth=3) to map every caller and callee, and detect_changes() to map your git diff to affected symbols. ## Quick Start Ask the agent to check whether the project is indexed with list_projects, then trace who calls a specific function using the codebase knowledge graph.High-intent search queries and answers about installing and using this skill.
Use trace_path with direction set to inbound to list every caller of a function. First run search_graph with a name pattern to get the exact function name, since trace_path requires precise names.
Run search_graph with max_degree set to 0 and exclude_entry_points set to true. This returns functions with no inbound or outbound call edges that are not entry points, which are dead code candidates.
Use query_graph with Cypher when you need to inspect actual edges such as HTTP_CALLS, since search_graph only filters nodes by degree. Note that query_graph caps results at 200 rows, so use search_graph for counting.
trace_path requires the exact function name, so a partial or misspelled name returns nothing. Run search_graph with a name_pattern first to discover the precise name, and verify the project is indexed with list_projects.
No, direction set to outbound misses cross-service callers. Use direction set to both, or write a Cypher query against HTTP_CALLS and ASYNC_CALLS edges to see cross-service relationships.
sambeauIndex repositories and search code graphs via MCP tools.
islamu-ngoGuides behavior-preserving structural refactoring with impact analysis, caller migration, and verification.
Corvalis-LLCCoordinate end-to-end project validation with a findings-first manual review.
89jobrienIndex repositories into a queryable knowledge graph using gkg.