speckit-ripple-scan

To find untested side effects from a git diff, perform a delta-anchored ripple analysis that compares your pre-implementation merge-base baseline against the current HEAD change set to discover newly introduced or worsened impacts across data flows and contracts.

Blast radius dependent tracing is an impact analysis technique that maps each changed file to its dependent files to locate where implicit contracts, altered data flows, and runtime assumptions are now at risk after an implementation change.

To scan implementation ripples by severity, run the ripple scan command and specify the argument as critical when you only want critical findings, evaluating risks across categories like data flow, performance, and concurrency.

Yes, you can analyze a specific change set incrementally by using the optional incremental --diff behavior, which extracts the change set via git diff to focus the ripple analysis solely on the targeted implementation delta.

A ripple scan evaluates test coverage gaps across multiple software risk categories including data flow, lifecycle state, interface contracts, performance, concurrency, distributed coordination, configuration, error propagation, and observability.

You need to run an impact analysis for deployment coordination issues when a feature implementation must be validated for untested impacts like broken implicit contracts, altered error semantics, or performance regressions that could cause production failures.