impact-analysis

To prevent breaking changes when modifying shared modules, enforce dependency awareness by verifying upstream callers, downstream dependencies, and contract impacts before executing code edits. This ensures signature expectations and interactions remain correct across the dependency graph.

Dependency analysis for API contract changes is the process of identifying upstream callers and downstream dependencies to detect signature, interface, or data-shape alterations. It validates test coverage and side-effect risks to ensure code modifications do not cascade failures across the codebase.

Perform a risk assessment before altering function signatures by running a verification checklist that reports upstream callers, downstream dependencies, contract changes, test coverage, and side effects. This generates a structured risk-based output to validate the safety of the code edits.

Yes, you can validate milestone work boundaries across multiple sessions by applying dependency awareness checks. This requires a consolidated analysis at milestone boundaries to ensure upstream and downstream dependencies remain stable throughout the editing process.

Yes, impact analysis works for detecting unintended state and IO mutations by applying contract and side-effect guardrails. It identifies data-shape changes and unintended state or IO mutations during the dependency verification process before code edits are finalized.