-
fix(pipeline): focus review fixer verification (#453)
frostbyte_neo 发布于
2026-07-11 23:19:59 +00:00 | 254 次提交 在此版本后已推送到 main- fix(pipeline): scope review fixer verification to the changed area
The review-fix prompt previously said only "Verify that the issues are
resolved before finishing", which invited the fixer agent to re-run the
whole repository test+lint suite after every fix. A forensic audit of a
real multi-round run measured 27 full-suite test/lint runs across 5 fixer
rounds, consuming ~784s inside a 2419s review step.The fixer contract now applies all fixes first, then runs one focused
verification limited to the changed area at the end of the round, and
never runs the complete repository test/lint suite. The dedicated Test
and Lint steps that run after review (pipeline order in steps/common.go:
review -> test -> ... -> lint) remain the authoritative full-suite gates.
This mirrors the "relevant"-scoped, cross-tool-forbidden discipline the
test and lint fix prompts already carry.Preserved unchanged: full-diff adversarial rereview, reviewer/fixer role
isolation, all findings, and the ask-user/intent conformance gates. The
reviewer is untouched.The instruction is a prompt contract, not an enforced sandbox (the fixer
agent has free shell access), so the regression pins the exact wording
rather than the runtime:
TestReviewStep_FixMode_FocusedVerificationContract.-
no-mistakes(review): Clarify focused review fixer verification coverage
-
no-mistakes(document): Document focused review-fixer verification
下载附件