Review changes with Niro
When a reviewer looks at a change, the question is what else it touches. Niro can answer that for the branch on the reviewer's own computer.
What works locally
With the branch checked out and its folder indexed, the reviewer (or the reviewer's coding agent) can ask four kinds of question:
- Who depends on each changed method:
get_blast_radiusorget_impact_analysis. - Whether a route was removed or changed:
find_api_endpoints, compared with the main branch's folder. - Whether a call to another service changed:
find_outbound_http_calls. - Which tests reach the changed code:
get_reverse_call_chain. Test callers are marked[test].
A new branch of a folder Niro already indexes gets its own copy of the graph automatically. See Worktrees and branches.
Review bots
Review bots, such as Cursor Bugbot or CodeRabbit, cannot use the local graph in this release. They run on someone else's servers, and the local engine is not reachable from there. See Review bots and Niro.
Pull request review as a product
Automatic pull request review is a hosted Niro feature. It runs on Niro's servers, against a copy of your code there, and the local graph does not answer it. See Features of hosted Niro.
Playbook
Review a change runs the whole check on an example two-method change in Keycloak: one get_blast_radius call with method_fqns for the size, one with answer=names for the list, then the routes and calls to other services compared with the main branch.