Skip to content

🤖 docs: bound the PR review loop by scope, not round count - #4208

Merged
ThomasK33 merged 3 commits into
mainfrom
agents-review-loop-scope
Sep 11, 2026
Merged

🤖 docs: bound the PR review loop by scope, not round count#4208
ThomasK33 merged 3 commits into
mainfrom
agents-review-loop-scope

Conversation

@ThomasK33

Copy link
Copy Markdown
Member

Summary

The PR Workflow section of AGENTS.md now bounds the Codex review loop by scope instead of by "iterate until clean". It adds two early-stop cases (the loop does not converge, or the next fix grows the scope) and a classification for review fixes that keeps a PR recognizable as the change it started as.

Background

PR #4139 grew from +447/-64 to +15.8k/-506 over 91 Codex rounds because every finding was fixed in place, including findings that needed new modules, on-disk artifacts, persisted fields, and second-backend races. The existing guidance had one early-stop case (reviewer misunderstands the change) and no scope rule. ThomasK33 asked for guidance that describes the shape of scope growth without hard numeric thresholds, written in plain English (short sentences, condition before command, numbered steps).

Implementation

Doc-only change to docs/AGENTS.md (the root AGENTS.md is a symlink):

  1. The single early-stop sentence becomes a three-item list: reviewer misunderstanding, non-converging loop, scope growth.
  2. New ### Review fixes and scope subsection: fix in place when small and inside the original change, otherwise reply on the thread, resolve, and deliver as a stacked PR (gh stack) or tracked follow-up. Findings that need corrupted persisted state, narrow crash windows, or a second racing backend are deferrable unless the PR introduced that surface. A reasoned rejection is a valid resolution.
  3. The mandatory-readiness block now points at the early-stop cases so the two paragraphs do not contradict each other.

Risks

None at runtime. Agent behavior changes: agents will pause and report a split proposal instead of growing a PR under review.


Generated with xum • Model: anthropic:claude-fable-5-1 • Thinking: high • Cost: $940.64

Add early-stop cases for non-converging review loops and a scope
classification for review fixes to the PR Workflow section of AGENTS.md.

---

_Generated with `xum` • Model: `anthropic:claude-fable-5-1` • Thinking: `high` • Cost: `$940.64`_

<!-- mux-attribution: model=anthropic:claude-fable-5-1 thinking=high costs=940.64 -->
@mintlify

mintlify Bot commented Sep 11, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
Mux 🟢 Ready View Preview Sep 11, 2026, 9:36 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 11, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-11T09:37:59.082045Z f910f6a Manual request
🔒 Security Review Completed 2026-09-11T09:39:52.761062Z f910f6a Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

---

_Generated with `xum` • Model: `anthropic:claude-fable-5-1` • Thinking: `high` • Cost: `$940.64`_

<!-- mux-attribution: model=anthropic:claude-fable-5-1 thinking=high costs=940.64 -->
@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: b7a6aa8d0b

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a60cdd0010

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/AGENTS.md Outdated
Comment thread docs/AGENTS.md Outdated
Comment thread docs/AGENTS.md Outdated
@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: a60cdd0010

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

Split the success prohibition from the stop exception, classify fixes
by whether this PR introduced the defect instead of by diff size alone,
and base deferral on the defect rather than its trigger condition.

---

_Generated with `xum` • Model: `anthropic:claude-fable-5-1` • Thinking: `high` • Cost: `$940.64`_

<!-- mux-attribution: model=anthropic:claude-fable-5-1 thinking=high costs=940.64 -->
@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: f910f6ae0a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: f910f6ae0a

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ThomasK33
ThomasK33 added this pull request to the merge queue Sep 11, 2026
Merged via the queue into main with commit 4fe8f96 Sep 11, 2026
36 of 39 checks passed
@ThomasK33
ThomasK33 deleted the agents-review-loop-scope branch September 11, 2026 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant