Software Development
Change Impact
Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare 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.
- Publisher / source
- affaan-m/ECC (found on skills.sh, an awesome list, the CSV list)
- Upstream record
- affaan-m/ECC
- Version
- Version 1
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-02
- Content fingerprint
b8d8a11417af8b84e93983a8eb682e3b9a16d04f926778eb635c96e90019bf18