Find every caller. See what a change touches.
Ask where a function is used, or what depends on a file. Prism answers from its map of your code: every caller, the files and tests a change reaches, and a risk band.
getUser function · src/users/api.ts
← src/pages/checkout.ts references · measured
← src/users/profile.ts references · measured
“Where do we call getUser?” uses graph in neighbors mode. In the terminal: prism refs.
Every caller
graph mode neighbors, direction in, lists who uses a function. Each edge says how it was found: measured, heuristic or inferred.
What a change touches
blast_radius lists the files and tests a change reaches, with a risk band: low, mid or high.
Tests to run
test_impact lists the tests that reach a change, with a ready command.
What depends on a file
“What depends on totals.ts?” Prism counts the files that depend on it and the tests that reach it.
Risk 40/100 Moderate Impact
Affected files 5 · Tests likely affected 2
Run the right tests
“Which tests cover totals.ts?” Prism lists them, nearest first.
2 test files reach src/billing/totals.ts
test/totals.test.ts · test/invoice.test.ts
Try it in your repo.
Install Prism, then connect every agent on this machine. Open the agent again.