2026-06-24 · issue-fix-workflow

PR issue automatic fix loop

Review feedback should become an ordered repair workflow with repro, fix, validation, and reviewer handoff.

The operator can turn a PR issue into a controlled fix loop without manually rewriting the review comment as an agent plan.

issue fixrepro smokePR review

Case context

This case turns a PR issue, review comment, or issue text into an executable repair loop. It is not simply reading a comment and editing code; the path goes through metadata/intake, repro, branch-local patch, validation, and review packet.

The user-facing value is that feedback no longer sits in a comment thread: it enters a loop with an owner, repro path, branch-local fix, validation, and review handoff. The public evidence proves the loop and its boundaries without exposing raw issue bodies, private timelines, or local paths.

Repository evidence

Proof

Issue and review feedback can enter an executable repair loop.

LoopX intervention

issue-fix workflow, command pack, repro smoke, PR review feedback

5repair-loop stages

1branch-ready fix packet

1review handoff preserved

0raw issue bodies in public artifact

Product entry

`docs/capabilities/issue-fix/README.md` names `loopx issue-fix ...`, the content-ops bridge, protocol docs, and smokes; the maintainer-facing action is turning feedback into an executable fix packet.

Workflow contract

`issue_fix_workflow_contract_v0` defines metadata preview, intake classification, workflow plan, todo writeback, caller repo branch, validation, PR review packet, and gate handling.

Executable loop

`issue_fix_acceptance_loop_v0` includes the acceptance fixture, repo-branch fixture, and caller-approved repo branch mode.

Validation surface

Focused smokes protect the key boundaries for metadata preview, content-ops intake, workflow plan, workflow contract, acceptance loop, and end-to-end workflow behavior.

LoopX behavior

1
Public metadata can enter packets; raw issue bodies, comment bodies, timelines, and provider payloads remain gated sources.
2
Accepted candidates become ordered LoopX todos: repro smoke, code-context route, branch-local patch, validation, and review-packet readiness.
3
Caller-approved repo mode inspects the local repo only under `--execute` and reports repo-relative changed files plus validation pass/fail.
4
External comments, PR creation, merge, publish, destructive git, and production action remain explicit gates.

What the user sees

A maintainer can provide a public issue or PR signal and get a loop that reproduces, fixes, validates, and prepares human review.

The user does not need to rewrite every review comment as an agent prompt, and raw issue bodies or local paths do not leak into the public artifact.

Repository sources

capability READMEdocs/capabilities/issue-fix/README.mdworkflow contractdocs/capabilities/issue-fix/protocols/issue-fix-workflow-contract-v0.mdacceptance loopdocs/capabilities/issue-fix/protocols/issue-fix-acceptance-loop-v0.mdworkflow smokeexamples/issue-fix-workflow-plan-smoke.pyacceptance smokeexamples/issue-fix-acceptance-loop-smoke.py

Evidence boundary. Public-safe pattern case only; no private screenshots, raw gated issue bodies, internal review notes, local paths, raw logs, credentials, or unpublished repository artifacts.

Case note