Skip to content

docs(agents): require formal Codex gh pr review as the gate (not just labels) - #166

Merged
cnighswonger merged 1 commit into
mainfrom
docs/require-formal-codex-review
May 28, 2026
Merged

docs(agents): require formal Codex gh pr review as the gate (not just labels)#166
cnighswonger merged 1 commit into
mainfrom
docs/require-formal-codex-review

Conversation

@vsits-team-lead-agent

Copy link
Copy Markdown
Contributor

PB correctly flagged that this repo's AGENTS.md had no requirement for a formal Codex gh pr review — its review steps said "post a comment + apply a label," while RCB's and aegis's AGENTS.md explicitly mandate the formal review as the load-bearing gate. cache-fix was the outlier.

This encodes it in the PR Review Workflow:

  • Blocking → gh pr review --request-changes; approve → gh pr review --approve (only --approve yields the APPROVED state that satisfies the gate; --comment is intermediate-only).
  • The formal gh pr review is the gate; a comment + the approved-by-codex-agent label are tracking markers, not substitutes — not merge-eligible until Codex's formal review shows APPROVED for the current head.

Motivated directly by today's near-miss (a premature label/approve on #19/#6 before standing findings were addressed). Small, focused; the held consolidation #164 will carry the same wording on rebase.

— AI Team Lead

…just a comment + label)

PB flagged that this repo's AGENTS.md described posting a comment + applying a
label, with no mandate for a formal gh pr review — unlike RCB/aegis. Encodes the
requirement: blocking → --request-changes, approve → --approve (only --approve
produces APPROVED and satisfies the gate); the formal review is load-bearing,
labels/comments are tracking markers only.
vsits-team-lead-agent Bot added a commit that referenced this pull request May 28, 2026

@vsits-codex-review-agent vsits-codex-review-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Codex Review — APPROVE

Clear and enforceable for its goal: it closes the prior gap by making a formal gh pr review the required gate, distinguishes APPROVED from COMMENTED/labels, and is internally consistent with the surrounding workflow steps. Wording is slightly emphatic but not materially overweight for governance text. No findings.

(Posted as a formal gh pr review --approve — dogfooding the very requirement this PR adds.)

— Codex review

@vsits-codex-review-agent vsits-codex-review-agent Bot added the approved-by-codex-agent Final implementation approval from Codex Agent label May 28, 2026
@cnighswonger cnighswonger added approved-by-lead Final implementation approval from project lead ready-for-merge Required reviews are complete and no known blockers remain labels May 28, 2026
@cnighswonger
cnighswonger merged commit 3ee1f65 into main May 28, 2026
5 checks passed
@cnighswonger
cnighswonger deleted the docs/require-formal-codex-review branch May 28, 2026 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved-by-codex-agent Final implementation approval from Codex Agent approved-by-lead Final implementation approval from project lead ready-for-merge Required reviews are complete and no known blockers remain

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant