pr-review-loop

Enforces Codex approval verification before merging GitHub pull requests.

4.0k|282|Updated Dec 2, 2024

Search Tags:#code review #pull request #github #codex #gh cli #merge gate #ci workflow

Ready to run

npx skills add https://github.com/basicmachines-co/basic-memory --skill pr-review-loop-basicmachines-co

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review-loop
Source: https://github.com/basicmachines-co/basic-memory/tree/main/.agents/skills/pr-review-loop
Command: npx skills add https://github.com/basicmachines-co/basic-memory --skill pr-review-loop-basicmachines-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents merging GitHub pull requests prematurely when CI is green but the Codex reviewer has not yet approved the latest head, avoiding post-merge review findings. ## Core Features & Use Cases - Approval Gate Enforcement: Blocks merging until Codex leaves a fresh thumbs-up reaction on the PR body or comment, or the user explicitly overrides the gate. - Multi-Surface Signal Inspection: Checks PR body reactions, issue comments, top-level reviews, and unresolved non-outdated review threads via the GitHub CLI and GraphQL API. - Feedback Loop Workflow: Guides addressing substantive Codex feedback with fixes or evidence-based replies, restarting the loop after every push. - Use Case: When a PR shows green checks and mergeable status, run this loop to confirm Codex actually approved the current head before running gh pr merge. ## Quick Start Ask the agent to check whether the Codex review gate is satisfied on the current pull request before merging.

Frequently Asked Questions about pr-review-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify Codex approval before merging a GitHub PR?▼

Check for a fresh thumbs-up reaction from chatgpt-codex-connector[bot] on the PR body or a Codex comment, created after the current head's checks started. Green CI and mergeable status alone are not approval signals.

Why is green CI not enough to merge a pull request?▼

Passing checks only prove tests pass, not that the reviewer approved the code. Codex may still be reviewing or may post blocking feedback after CI completes, so merging early can land unreviewed changes.

Can I merge a PR without waiting for Codex approval?▼

Yes, but only with an explicit user override such as "merge without waiting for Codex approval". The gate then reports as overridden, and the merge proceeds only if tests pass on the same head.

What GitHub API surfaces does Codex leave review signals on?▼

Codex leaves signals on PR body reactions, issue comments, top-level pull request reviews, and inline review threads. Each surface requires separate REST or GraphQL queries since reaction counts do not identify the reacting user.

What happens to Codex approval after pushing new commits?▼

Any push after a prior approval invalidates it because the review applied to the old head. The loop restarts from scratch, requiring a fresh Codex response on the new head SHA before merging.