Hivemind Code Graph

A deterministic, AST-derived map of the current repository, every function, class, method, interface, type, enum, const, and module, plus the edges between them (calls, imports, extends, implements, method_of). It is queried as synthesized files under the Deeplake mount; there are no real files on disk and no network call in the read path.

The graph builds and refreshes automatically (on Stop / SessionEnd, gated by a rate limit + git diff). You never run a build command, just read it.

Use it as a fast INDEX to locate the few files/symbols that matter, then open them with Read to answer. It is not a substitute for the source.

When to use this skill

Activate when the user asks a structural / relational question about the code:

• "What calls pushSnapshot?" / "Who uses this function?"
• "What does deeplake-pull.ts import?" / "What depends on X?"
• "Where is GraphSnapshot defined?" / "Find the function that handles Y."
• "What are the main subsystems / the architecture here?"
• "If I change this signature, what's affected?" → use impact/<symbol> (transitive blast radius)

When NOT to use this skill

• Reading the body of a symbol you already located → use Read on the real source file. The graph gives location + relationships, not full source.
• Code that isn't committed/built yet, the graph can lag uncommitted edits. If a file's mtime is newer than the build timestamp, read the live source.
• Languages outside TypeScript, JavaScript, and Python (Go, Rust, …), the extractor covers those three, with cross-file calls/imports resolved for named imports. For anything else, fall back to grep/read.

Path cheat sheet

cat ~/.deeplake/memory/graph/index.md
#   Overview: node/edge counts, kind breakdown, top files by node count.