speckit-ripple-check

To verify code fixes without introducing new ripple effects, re-check each OPEN item against the current codebase to mark it as resolved, mitigated, worsened, or stale based on evidence. This post-scan maintenance confirms whether your refactoring safety changes worked without side effects.

A ripple check in static analysis is a re-verification workflow that reloads an existing audit report and re-evaluates each OPEN finding by reading the current code. It detects resolution quality and scans changed lines for newly introduced side effects.

Update an audit report after fixing static analysis findings by loading the existing ripple-report.md, filtering by severity or finding ID, and modifying the report in place. This recalculates counts, updates the Coverage Gap Matrix, and appends a deduplicated Check History row.

Yes, you can filter code verification re-checks by severity and finding ID. This allows you to target specific items, such as running a check on only CRITICAL OPEN findings to efficiently update the report with evidence-based verdicts.

Re-verifying regression detection findings produces RESOLVED, MITIGATED, OPEN, WORSENED, or STALE outcomes. These verdicts are based on whether the side effect still exists, was reduced, worsened, or became unavailable due to refactoring.

Use a ripple check for refactoring safety after you change code post-scan and need to confirm whether fixes worked. It prevents verification drift by ensuring your changes did not introduce new side effects in the updated codebase.