impact-review

Code Review + Impact-of-Change Analysis

Goes one step beyond a normal review: not just "is this code correct" but "what does changing it put at risk".

Steps

1. Get the change scope: git diff (staged/working tree, or against base branch).

2. Correctness pass (see also the code-reviewer agent for a dedicated read-only pass): logic errors, edge cases, error handling, test coverage gaps.

3. Impact / blast-radius pass — for each changed function/type/endpoint/schema:

   • Find call sites / consumers: grep/rg for the symbol across the repo (and across services if it's a shared contract — API, schema, shared package)
   • Identify anything that assumes the old behavior (return type, error conditions, side effects, ordering, performance characteristics)
   • Flag changes to shared/public surfaces (exported APIs, DB schemas, queue message formats) as higher-risk than internal-only changes

4. Summarize:

   ## Correctness
   <findings, or "no issues found">
   
   ## Blast radius
   - Direct consumers: <files/services that call the changed code>
   - Risk level: <low/medium/high — and why>
   - Things to verify before merging: <specific checks — e.g. "run the
     billing integration suite, it depends on this return shape">
   

Notes

• This is a local review — run it on your working changes before opening a PR, not as a substitute for CI.
• "No consumers found" is itself a useful finding — it might mean dead code, or it might mean the search missed cross-service usage; say which you suspect.