Change Impact Analysis
Overview
Change Impact Analysis is the evidence-first discipline of mapping who and what a code, data, interface, or governance change will affect BEFORE executing it, then reconciling the actual diff against the plan. It prevents production outages, silent contract violations, and irreversible migrations by enforcing read-only dependency discovery (git grep, AST queries, import mappings) over intuition, and by attaching rollback steps and verification commands to every change.
Read-only by default. Use git grep, ast_grep, find, and read to map dependencies—never assume directory structures or model intuitions.
When to Use
Trigger phrases:
- "change impact"
- "impact analysis"
- "blast radius"
- "affected callers"
- "migration risk"
Use directly when:
- Planning cross-module, public-interface, or data-migration changes.
- Pre-change: want to know who/what will be affected by a proposed diff.
- Post-change: verify the actual diff matches the planned impact.
- Auditing authentication, API, or schema modifications.
- Assessing rollback feasibility and recovery steps.
When NOT to Use
- Single-file, low-risk refactors without cross-module dependencies.
- When a targeted linter/formatter check suffices (e.g., unused imports).
- For debugging test failures—use
test-agent instead.
Anti-Rationalization Table
| Rationalization |
Reality |
| "I'll just make the change and see what breaks." |
Unverified changes cause production outages without recovery paths. Plan first, execute second. |
| "The caller will figure it out if their code breaks." |
Silent contract violations cascade into data corruption, security gaps, or billing discrepancies. |
| "I can grep the directory name for dependencies." |
Directory names are not call signatures. Use git grep on function names, AST queries, or import mappings. |
| "This is just a rename, no big deal." |
Renames affect imports, routes, API contracts, tests, docs, and ADRs. Map all before renaming. |
Workflow
1. Establish Evidence Sources (Read-Only)
Query authoritative sources for dependency mapping:
# Callers / imports
git grep -n "import.*from.*${COMPONENT}" -- '*.{py,ts,js}'
ast-grep --pattern "from '$COMPONENT'" # or JS import/export patterns
# API routes
grep -r "get|post|put|delete.*'/$COMPONENT" -- '*.py' # FastAPI/Express
grep -r "$COMPONENT:" # Diesel/Rust or Rust routers
# Tests
git ls-files | xargs grep -l "test.*$COMPONENT"
2. Map Impacted Surfaces
| Surface |
Evidence Method |
| Code |
git grep for callers, AST for call graphs, import statements |
| Data |
Schema files, migrations, type definitions, ORM models |
| Interfaces |
OpenAPI specs, GraphQL schemas, REST route tables |
| Tests |
TEST_IDS.md, pytest markers, Jest test files |
| Documentation |
ADRs, CHANGELOG, README, internal wiki links |
| Deployment |
systemd units, Dockerfiles, k8s manifests, CI/CD configs |
| Rollback |
Migration scripts, backup procedures, revert commands |
3. Route to Specialized Skills (Deterministic Dispatch)
| Impact Type |
Delegated Skill |
| API contract changes |
api-contract-drift-audit |
| Database migration |
prisma-migration-ledger-reconcile, zero-downtime-migration-audit |
| Authentication/auth changes |
auth-patterns, jwt-token-security |
| Front-end component change |
frontend-design, impeccable |
| DevOps / deployment |
devops/, systemd-deploy-parity-verify |
| Documentation / ADR |
docs-governance, contract-manager |
| Test strategy |
agent-reach, test-agent, test-coverage-analyzer |
4. Plan Mitigation Steps
For each impacted surface, identify:
- Owner / reviewer
- Verification command or checklist
- Rollback procedure
- Communication timeline
5. Execute & Compare Diff
After changes:
git diff --stat
git diff HEAD~1 --name-only # only changed files
git diff HEAD~1 -- '*.{py,ts,js}' # code only
Reconcile planned impacts with actual diff and report:
- Scope drift (missing/added files)
- Unverified consumers
- Unfixed breakages
- Remaining risk
Verification Checklist
1---2name: change-impact-analysis3description: Use when performing evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then comparing the planned impact with the actual diff after implementation. Covers call paths, data and schema, API contracts, tests, documentation, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.4domain: development5subdomain: devsecops6category: development7version: 1.0.08author: oyi779license: Apache-2.010tags:11- impact-analysis12- risk-assessment13- planning14- change-management15- blast-radius16triggers:17- change impact18- impact analysis19- blast radius20- affected callers21- migration risk22- pre change check23argument-hint: "file_path OR component_name"24metadata:25 source: https://skillmd.com/skills/oyi77/change-impact-analysis26---2728# Change Impact Analysis2930## Overview3132Change Impact Analysis is the evidence-first discipline of mapping who and what a code, data, interface, or governance change will affect BEFORE executing it, then reconciling the actual diff against the plan. It prevents production outages, silent contract violations, and irreversible migrations by enforcing read-only dependency discovery (`git grep`, AST queries, import mappings) over intuition, and by attaching rollback steps and verification commands to every change.3334Read-only by default. Use git grep, ast_grep, find, and read to map dependencies—never assume directory structures or model intuitions.3536## When to Use3738**Trigger phrases:**39- "change impact"40- "impact analysis"41- "blast radius"42- "affected callers"43- "migration risk"4445Use directly when:46- Planning cross-module, public-interface, or data-migration changes.47- Pre-change: want to know who/what will be affected by a proposed diff.48- Post-change: verify the actual diff matches the planned impact.49- Auditing authentication, API, or schema modifications.50- Assessing rollback feasibility and recovery steps.5152## When NOT to Use5354- Single-file, low-risk refactors without cross-module dependencies.55- When a targeted linter/formatter check suffices (e.g., unused imports).56- For debugging test failures—use `test-agent` instead.5758## Anti-Rationalization Table5960| Rationalization | Reality |61|---|---|62| "I'll just make the change and see what breaks." | Unverified changes cause production outages without recovery paths. Plan first, execute second. |63| "The caller will figure it out if their code breaks." | Silent contract violations cascade into data corruption, security gaps, or billing discrepancies. |64| "I can grep the directory name for dependencies." | Directory names are not call signatures. Use `git grep` on function names, AST queries, or import mappings. |65| "This is just a rename, no big deal." | Renames affect imports, routes, API contracts, tests, docs, and ADRs. Map all before renaming. |6667## Workflow6869### 1. Establish Evidence Sources (Read-Only)7071Query authoritative sources for dependency mapping:7273```bash74# Callers / imports75git grep -n "import.*from.*${COMPONENT}" -- '*.{py,ts,js}'76ast-grep --pattern "from '$COMPONENT'" # or JS import/export patterns7778# API routes79grep -r "get|post|put|delete.*'/$COMPONENT" -- '*.py' # FastAPI/Express80grep -r "$COMPONENT:" # Diesel/Rust or Rust routers8182# Tests83git ls-files | xargs grep -l "test.*$COMPONENT"84```8586### 2. Map Impacted Surfaces8788| Surface | Evidence Method |89|---|---|90| **Code** | `git grep` for callers, AST for call graphs, import statements |91| **Data** | Schema files, migrations, type definitions, ORM models |92| **Interfaces** | OpenAPI specs, GraphQL schemas, REST route tables |93| **Tests** | `TEST_IDS.md`, pytest markers, Jest test files |94| **Documentation** | ADRs, CHANGELOG, README, internal wiki links |95| **Deployment** | systemd units, Dockerfiles, k8s manifests, CI/CD configs |96| **Rollback** | Migration scripts, backup procedures, revert commands |9798### 3. Route to Specialized Skills (Deterministic Dispatch)99100| Impact Type | Delegated Skill |101|---|---|102| API contract changes | `api-contract-drift-audit` |103| Database migration | `prisma-migration-ledger-reconcile`, `zero-downtime-migration-audit` |104| Authentication/auth changes | `auth-patterns`, `jwt-token-security` |105| Front-end component change | `frontend-design`, `impeccable` |106| DevOps / deployment | `devops/`, `systemd-deploy-parity-verify` |107| Documentation / ADR | `docs-governance`, `contract-manager` |108| Test strategy | `agent-reach`, `test-agent`, `test-coverage-analyzer` |109110### 4. Plan Mitigation Steps111112For each impacted surface, identify:113- Owner / reviewer114- Verification command or checklist115- Rollback procedure116- Communication timeline117118### 5. Execute & Compare Diff119120After changes:121122```bash123git diff --stat124git diff HEAD~1 --name-only # only changed files125git diff HEAD~1 -- '*.{py,ts,js}' # code only126```127128Reconcile planned impacts with actual diff and report:129- Scope drift (missing/added files)130- Unverified consumers131- Unfixed breakages132- Remaining risk133134## Verification Checklist135136- [ ] Dependency mapping completed via `git grep` or AST queries137- [ ] No inferred dependencies (verified by import paths, not directory names)138- [ ] All impacted test files identified and linked139- [ ] ADR and documentation updates planned/scheduled140- [ ] Rollback procedure documented with exact recovery commands141- [ ] Post-implementation diff matches planned impact (no scope drift)142- [ ] Zero unverified callers/consumers