Codebase memory
A set of zsh, git, bash, Claude and tmux configuration files
npx -y skills add ccronca/dotfiles --skill codebase-memoryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions, high fan-out, refactor candidates, code quality audit, graph query syntax, Cypher query examples, edge types, how to use search_graph.
SKILL.md
3.1 KB, as published. Nobody here has run it
Codebase Memory — Knowledge Graph Tools
Graph tools return precise structural results in ~500 tokens vs ~80K for grep.
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() |
| Risk-classified trace | trace_path(risk_labels=true) |
| Text search | search_code or Grep |
Exploration Workflow
list_projects— check if project is indexedget_graph_schema— understand node/edge typessearch_graph(label="Function", name_pattern=".*Pattern.*")— find codeget_code_snippet(qualified_name="project.path.FuncName")— read source
Tracing Workflow
search_graph(name_pattern=".*FuncName.*")— discover exact nametrace_path(function_name="FuncName", direction="both", depth=3)— tracedetect_changes()— map git diff to affected symbols
Quality Analysis
- Dead code:
search_graph(max_degree=0, exclude_entry_points=true) - High fan-out:
search_graph(min_degree=10, relationship="CALLS", direction="outbound") - High fan-in:
search_graph(min_degree=10, relationship="CALLS", direction="inbound")
14 MCP Tools
index_repository, index_status, list_projects, delete_project,
search_graph, search_code, trace_path, detect_changes,
query_graph, get_graph_schema, get_code_snippet, get_architecture,
manage_adr, ingest_traces
Edge Types
CALLS, HTTP_CALLS, ASYNC_CALLS, IMPORTS, DEFINES, DEFINES_METHOD, HANDLES, IMPLEMENTS, OVERRIDE, USAGE, FILE_CHANGES_WITH, CONTAINS_FILE, CONTAINS_FOLDER, CONTAINS_PACKAGE
Cypher Examples (for query_graph)
MATCH (a)-[r:HTTP_CALLS]->(b) RETURN a.name, b.name, r.url_path, r.confidence LIMIT 20
MATCH (f:Function) WHERE f.name =~ '.*Handler.*' RETURN f.name, f.file_path
MATCH (a)-[r:CALLS]->(b) WHERE a.name = 'main' RETURN b.name
Gotchas
search_graph(relationship="HTTP_CALLS")filters nodes by degree — usequery_graphwith Cypher to see actual edges.query_graphhas a 200-row cap — usesearch_graphwith degree filters for counting.trace_pathneeds exact names — usesearch_graph(name_pattern=...)first.direction="outbound"misses cross-service callers — usedirection="both".- Results default to 10 per page — check
has_moreand useoffset.
Gives 0 of the 12 instructions most memory context skills give
Counted across 674 of the 847 authors here whose files we hold, read 2026-08-06
- inform the user when setup is completein 21 of 674, across 6 files
- confirm the draft with the user before writingin 21 of 674, across 6 files
- update the agent skills block in place if it existsin 21 of 674, across 6 files
- present findings to the userin 20 of 674, across 5 files
- write the three docs files from seed templatesin 20 of 674, across 5 files
- ask the user about each decision one at a timein 19 of 674, across 4 files
- edit CLAUDE.md if it existsin 18 of 674, across 3 files
- explore current repo statein 18 of 674, across 3 files
- do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
- back up the original file before overwritingin 16 of 674, across 8 files
- keep the memory index under 200 linesin 15 of 674
- Provide actionable steps and verificationin 13 of 674, across 2 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.