pr-iteration

Automating a GitHub pull request review cycle without auto-merging involves orchestrating end-to-end iterations that coordinate external reviews, CI polling, thread triage, and iterative fixes. This workflow drives the PR to a green terminal state while ensuring merges occur only under human approval.

Triageing code review threads and applying fixes across multiple rounds is done through an end-to-end PR iteration loop. This process monitors CI checks, triages review threads, and applies local code changes iteratively until all exit conditions are satisfied.

Yes, you can use GitHub GraphQL integration to track PR review state and generate per-round reports. This workflow supports GitHub tracker integration and outputs per-round reporting under the `.development/shared/reports` directory for team visibility.

Yes, this PR iteration workflow supports stateful progression for tracking review cycles. It maintains local JSON state under `.development/local/pr-iteration` to track the progression of external reviews, local code changes, and CI checks across multiple rounds.

You should not use automated end-to-end PR review orchestration if your project requires immediate auto-merging upon CI success, as this workflow explicitly avoids auto-merging. It is designed for projects needing human oversight, thread triage, and iterative fixes before final approval.