Summary
What breaks if I change this becomes a lookup rather than a guess.
An assistant reading files one at a time cannot see callers. With the graph loaded it can: the impact tool answers from the actual call structure, and the dependency tool does the same for modules and files. It holds several repositories at once, which matters when the caller lives in another service.
What it is
A call-graph server built on the nuanced library. It initialises a graph for a Python repository, then answers what calls what, what a file depends on, and what a change would touch.
What you get
- A code graph initialised for a repository path
- More than one repository held at once, with a switch between them and a listing of what is loaded
- The call graph for a named function in a named file
- Module and file dependencies across the codebase
- The impact of changing a specific function
- Graph and function summaries available as resources, plus prompts for function analysis, impact analysis and dependency review
Requirements
Python repositories on local disk - the graph is built from a repository path you give it, and analysis covers Python code.