change-impact-check

Change Impact Check

Code changes rarely exist in isolation. Before declaring success, you must evaluate the downstream consequences of your work.

API Surface: Did you change a public method signature, REST endpoint, or database schema? If so, immediately grep the entire repository for usages of the old signature.
Dependency Graph: If you updated a core utility function (e.g., formatDate), find all modules that import it. Do their tests still pass?
Configuration: Did you add a new environment variable? Ensure it is documented in .env.example or the README.md.
Action: If you detect a high blast radius, run the full test suite (not just the local unit tests) and explicitly document the affected areas in your handoff or PR description.

Code changes rarely exist in isolation. Before declaring success, you must evaluate the downstream consequences of your work.

API Surface: Did you change a public method signature, REST endpoint, or database schema? If so, immediately grep the entire repository for usages of the old signature.
Dependency Graph: If you updated a core utility function (e.g., formatDate), find all modules that import it. Do their tests still pass?
Configuration: Did you add a new environment variable? Ensure it is documented in .env.example or the README.md.
Action: If you detect a high blast radius, run the full test suite (not just the local unit tests) and explicitly document the affected areas in your handoff or PR description.