What problem does it solve? Review-and-fix requests often degrade into unbounded edit cycles with lost findings, unverified repairs, and no record of what was validated. This Skill drives a bounded, persisted loop where an executable controller owns round limits, provider attempts, validation, patch application, and terminal decisions, so every repair is evidence-backed and every outcome is recorded. ## Core Features & Use Cases - Controller-owned loop: A Node.js controller manages state, immutable assignments, round budgets (1-10), provider attempt caps, and terminal outcomes such as CONVERGED, BLOCKED, or VALIDATION_FAILED. - Isolated multi-provider review: Fresh isolated reviewers (native Codex or configured JSON adapters) receive only their assignment and a repository copy, with balanced or strict review policies. - Repair modes: Minimal, balanced, and comprehensive fix modes control investigation breadth while always requiring a causal repair at the responsible layer. - Journaled patch application: Repairs are captured as content-addressed candidates, applied with a recoverable journal, and validated with the repository's own checks; failed candidates remain visible without automatic rollback. - Use Case: Ask the agent to review and fix your working changes; it pins a task contract with acceptance criteria and validation commands, runs isolated reviews, repairs actionable findings, re-validates, and reports a terminal outcome with changed files and evidence. ## Quick Start Ask the agent to review and fix your current working changes, and it will initialize the controller, run the bounded repair loop, and report the terminal outcome with validation results.
