Code Change Impact — blast-radius / regression analysis

What I do

• Trace reverse dependencies from a changed symbol to every caller, importer, and consumer
• Hunt silent behavioral ripples the compiler can't catch
• Run the project's own typecheck, build, test, and lint to prove nothing broke
• Deliver a structured verdict: SAFE, SAFE WITH CAVEATS, or IMPACT FOUND

Run it against the VCS diff — it adapts to whatever language and tooling the repo uses by discovering the project's conventions first.

When to use me