Change Impact Analysis
Trace what a change can affect beyond its immediate diff.
Workflow
- Pin the exact change, base revision, intended outcome, and deployment or migration shape.
- Identify changed interfaces, behavior, data, configuration, permissions, dependencies, and timing assumptions.
- Trace direct callers and consumers, then indirect effects through shared types, events, schemas, caches, jobs, clients, reports, and operational controls.
- Check compatibility across independent upgrade order, partial rollout, rollback, retry, replay, and mixed-version states.
- Classify impacts as
Confirmed, Possible, or Cleared, and attach the evidence that supports each classification.
- Prove the highest-risk facts with focused tests, static queries, or safe read-only inspection when available.
- Report untraced surfaces and the owner or evidence needed to clear them.
Boundaries
- A textual match is a lead, not proof of a runtime dependency.
- Do not claim no impact outside the reviewed scope.
- Use API compatibility or authority review when those specialized contracts dominate the question.
- Do not deploy, migrate, merge, or notify stakeholders without separate authority.
Output
Return Change, Confirmed impacts, Possible impacts, Cleared surfaces, Evidence, Required tests, Rollout and rollback concerns, and Coverage gaps.
1---2name: change-impact-analysis-23description: Analyze the blast radius of a proposed or completed change across callers, contracts, storage, jobs, clients, security, rollout, and operations. Use before review, merge, or release when downstream effects may be missed; do not substitute speculation for traced dependencies.4license: MIT5---67# Change Impact Analysis89Trace what a change can affect beyond its immediate diff.1011## Workflow12131. Pin the exact change, base revision, intended outcome, and deployment or migration shape.142. Identify changed interfaces, behavior, data, configuration, permissions, dependencies, and timing assumptions.153. Trace direct callers and consumers, then indirect effects through shared types, events, schemas, caches, jobs, clients, reports, and operational controls.164. Check compatibility across independent upgrade order, partial rollout, rollback, retry, replay, and mixed-version states.175. Classify impacts as `Confirmed`, `Possible`, or `Cleared`, and attach the evidence that supports each classification.186. Prove the highest-risk facts with focused tests, static queries, or safe read-only inspection when available.197. Report untraced surfaces and the owner or evidence needed to clear them.2021## Boundaries2223- A textual match is a lead, not proof of a runtime dependency.24- Do not claim no impact outside the reviewed scope.25- Use API compatibility or authority review when those specialized contracts dominate the question.26- Do not deploy, migrate, merge, or notify stakeholders without separate authority.2728## Output2930Return `Change`, `Confirmed impacts`, `Possible impacts`, `Cleared surfaces`, `Evidence`, `Required tests`, `Rollout and rollback concerns`, and `Coverage gaps`.
JovaniPink