Alubiama Change Impact Checker
Goal
Catch regressions early by mapping blast radius before changes.
Impact Workflow
- Identify target files/components.
- Map direct and indirect dependencies.
- Estimate regression risk (
low/medium/high). - Define required tests/checks before and after.
- Recommend smallest safe change order.
Risk Signals
- Touching shared libraries or critical paths.
- Changing auth, billing, state, data writes, or scheduling.
- Updating dependencies with unknown compatibility.
Output Contract
Always output:
affected_componentsrisk_levelrequired_validationsafe_change_order
Guardrails
- Do not skip validation steps for medium/high impact changes.
- Escalate uncertainty when impact cannot be estimated confidently.