fix

Automating code review follow-up fixes involves executing planned fix instructions item by item or in parallel batches, verifying each change with a reviewer before committing. This ensures repository updates are applied consistently and safely without manual coordination.

Turning planned findings into verified code changes requires an implementer-plus-reviewer loop that applies each fix instruction, checks the result against the plan, and commits per-item. This workflow handles dirty working tree checks and staleness verification for safe completion.

Directive-aware agent dispatch routes specific fix instructions to designated agents for execution, then validates the output through a reviewer. It groups related fixes into parallel batches when safe, ensuring each repository change is verified before acceptance.

Running parallel fix batches requires clean working tree checks to prevent conflicts. The workflow performs staleness checks and handles per-item commits, ensuring each grouped fix applies safely without overwriting uncommitted repository changes.

Automated repository fixes fail when instructions are stale or the working tree is dirty. The workflow includes staleness checks and retry behavior with escape-hatch options, allowing you to safely handle tricky fixes that cannot be automatically verified.

Pre-planned fix instructions are required to automate repository changes safely. The workflow reads these per-finding directives, applies them individually or in grouped batches, and uses an implementer-reviewer verification loop to ensure accurate code changes.