simplify-loop

Automating iterative code refinement is done by repeating the built-in /simplify loop until convergence. This automatically runs cycles of code improvement and rule consolidation, stopping when no modifications are detected or a hard cap of ten iterations is reached.

The maximum iteration limit for an automated simplify workflow is a hard cap of ten cycles. This prevents endless loops during iterative convergence, ensuring the code review and rule consolidation process terminates even if continuous modifications are detected.

Yes, you can use project override files to customize the simplify automation rules. The workflow is override-aware and reads local configurations from .claude/be-harness, applying these extra rules or exceptions and prioritizing them on conflicts during iterative review.

Convergence detection in an iterative code simplification loop works by checking for modifications after each cycle. The automation continues executing the built-in /simplify loop until a complete pass detects no changes, indicating that iterative convergence has been achieved.

Yes, the be-harness workflow supports reporting outcomes for each code review cycle. As the automated simplify loop executes up to ten iterations, it reports the specific outcomes for every cycle, providing visibility into the iterative refinement process.