impact
Show what else breaks or needs retesting if you change a file or function.
Use it before editing ingested code, or to review a change: it walks
the code graph built at ingest. For "why is it built this way" ask
query; to see which repos are ingested use list_repos. Returns
{target, label, found, direct_callers, direct_callees, affected_files, affected_tests, transitive_nodes, transitive_count, paths, path_facts}; path_facts gives each sample path's hops,
dependents and whether it ends in a test. found: false means the
target is not in the graph, so check the spelling or ingest the repo.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| depth | No | How many call hops to follow out from the target, e.g. 3. Default 2; values below 1 count as 1. Higher finds more but returns a bigger result. | |
| target | Yes | What you plan to change: a file path as ingested, e.g. "micrograd/engine.py"; a function as "file::name", e.g. "engine.py::backward"; or a graph node id or wiki page name. Required. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||