loop

An iterative evaluation-fix-validate loop works by repeatedly assessing codebase findings, applying fixes selected by severity, and validating results per iteration. This cycle continues until the code quality converges on a stable state across the defined feature scope.

Start iterative code evaluation by running the loop command with your defined feature scope. This initiates the automated cycle of assessing findings, applying severity-selected fixes, and validating results to systematically improve your codebase quality.

Yes, automated code quality loops require a configured toolkit.toml file and an accessible codebase. These prerequisites allow the system to track scope, iterations, findings, and state across multiple runs to ensure controlled convergence.

Iterative code validation controls scope growth using per-iteration and total file limits to prevent explosion. Complex findings are deferred or branched, allowing the primary loop to converge on code quality without being blocked by edge cases.

The best way to converge on code quality for a large feature scope is using an automated evaluate-fix-validate loop. It selects fixes by severity, controls scope evolution with file limits, and commits validated improvements per iteration until stability.