Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Skip to main content
Ask better graph questions
[Local] Use query, path, and explain for different kinds of codebase questions.
Start with a specific subsystem or concept, then narrow your investigation. A compact query is usually more useful to an assistant than the whole architecture report.
Look at its source, community, and incoming and outgoing relationships. Inspect the source itself when a precise implementation detail matters.
This uses the tutorial’s example project. In your project, replace the labels with real nodes. Stored direction is respected; add
Gather context with query
graphify query "authentication and session storage" --budget 1500
query finds relevant starting nodes and traverses their relationships. Breadth-first traversal gathers a broader neighborhood. --dfs follows a deeper chain:
graphify query "request validation" --dfs --budget 1500
Inspect one concept with explain
Take a label or node ID from the query results:graphify explain "normalize_email"
Trace a relationship with path
graphify path "login" "normalize_email"
--undirected when you want connectivity rather than a directional path.
Ask the assistant to preserve uncertainty
Use Graphify to trace how a request reaches persistence. Show the path and source references. Flag inferred or ambiguous edges, and tell me if the graph is missing evidence.The tool supplies context, and the assistant interprets it. Ask for evidence and avoid treating an absent path as proof that two systems are independent.
Assistant
Responses are generated using AI and may contain mistakes.
