sdcorejs-repair-loop

Automating lint and typecheck fixes requires a closed-loop repair process that verifies findings, applies batch edits, and re-runs checks until Critical and Important issues are resolved. This prevents manual re-verification churn by iterating up to three times.

A fix loop for code review findings is an automated cycle that verifies each issue, categorizes it into fix tiers, applies mechanical fixes, and re-verifies the source. It converges by resolving or deferring Critical and Important items within three iterations.

When code review findings keep failing re-verification after three automated iteration passes, the repair loop escalates the non-convergent issues to the user. This guardrail prevents infinite loops and prompts manual intervention for unresolved items.

Yes, you can batch edit code to resolve linter and typecheck findings automatically by applying a tiered fix strategy. The system auto-applies mechanical issues, shows diffs for confirmation items, and defers architectural decisions.

Repair automation supports manual human-reported issues by selecting source-aligned re-verification commands. It processes findings from manual reports, linters, or review tracks, categorizes them, and iterates fixes until convergence.

Verifying code review findings before applying automated fixes ensures each issue is genuine, preventing mis-scoped or redundant changes. This validation step avoids unnecessary code churn and maintains source integrity during the repair loop.