Use cases / New team members and cross-team reviewers
Reviewing code you did not write in a system you do not know
A reading order: what is depended on before what depends on it.
The problem
Reading a diff top to bottom in alphabetical order is the worst possible order for understanding it.
What visualdiff does
- The reading order follows the dependency graph: data and shared code first, then domain, then entry points.
- The change map shows where each file sits and what imports it.
- Each plan item says why it is there: sensitive area, finding, new code, high fan-in.
Every plan item carries its reasons; the reading order is computed, not alphabetical.
Related
- Reviewing pull requests written by agentsAgents open pull requests faster than anyone can read them. Read the 10% that decides whether it is safe.
- Large refactors that hide a behaviour changeA refactor is supposed to change nothing. Find the one line that does.
- Stopping hallucinated dependenciesSlopsquatting: attackers register the package names models invent. Catch them at review.
- Seeing which running systems a change reachesThe diff says rds.tf. The map says orders-db, the API in front of it, and the queue behind it.