sdcorejs-repair-loop

What problem does it solve?

A review or verification that produces findings without an effective closed-loop fix cycle wastes time and creates churn, because issues must be validated, fixed, and re-checked against the same source of truth.

Core Features & Use Cases

• Finding verification first: Verifies each finding is genuine before touching code to avoid mis-scoped or redundant changes.
• Tiered fix strategy: Auto-applies mechanical issues, shows diffs for confirm-then-apply items, and defers architectural/user-decision items.
• Source-aligned re-verification: Re-runs the correct re-check flow based on findings origin (review-code, verify-before-done, linter, or manual), then iterates until Critical + Important are resolved or deferred.
• Loop convergence guardrails: Hard-caps at 3 iterations and escalates to user when findings do not converge.

Quick Start

Invoke sdcorejs-repair-loop after sdcorejs-review-code-<track> or verify-before-done outputs findings by providing the findings list and the correct source value so the re-verify step runs for the same context.