codex-pr-review-loop

Automates Codex review request, wait, fix, and re-review loops for GitHub pull requests.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill codex-pr-review-loop-ryokuman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-pr-review-loop
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/codex-pr-review-loop
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill codex-pr-review-loop-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing AI code review on GitHub pull requests is repetitive and error-prone: you must classify the PR by branch hierarchy, request a Codex review, wait for results, triage P2+ findings, fix or defend them, and repeat until the latest head passes. This Skill turns that into a deterministic loop with explicit exit criteria. ## Core Features & Use Cases - Hierarchy-aware PR classification: Distinguishes layer-0 common changes from project-layer changes, validates target/base branches, and prevents direct commits to project main branches. - Codex review loop with timeouts: Calls @codex review, watches for eyes reactions, retries unacknowledged calls up to 3 times, enforces 15-minute response timeouts, and can delegate waiting to a review-waiter agent. - P2+ finding triage: Classifies Codex findings on the current head as fix-required, defensible (with recorded evidence), or user-decision-required, and resolves stale review threads with documented justification. - Fallback and handoff paths: When Codex review is not configured, records the fallback evidence and runs runtime health checks and silo runtime handoff for product-code PRs. - Use Case: After pushing a feature branch, ask the agent to open a PR and drive it to a Codex pass; the loop fixes actionable findings, defends justified ones with evidence, and only exits when the latest head is clean. ## Quick Start Ask the agent to create a pull request for the current branch and run the Codex review loop until the latest head has no remaining P2 or higher findings.

Frequently Asked Questions about codex-pr-review-loop

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

FAQPage Schema
How do I automate Codex code review on a GitHub pull request?

Post an `@codex review` comment on the PR targeting the latest head SHA, then wait for the eyes reaction and review result. This Skill automates that loop: it retries unacknowledged calls, triages findings, applies fixes, pushes, and re-requests review until the latest head passes.

How does the skill decide when a Codex review loop can exit?

The loop exits only when Codex explicitly responds with 'Didn't find any major issues' or an equivalent pass for the current head SHA, and no unresolved P2/P1/major/critical findings remain on that head. Defended findings must have recorded evidence from user decisions, contracts, or PR scope.

What happens if Codex review is not configured on my repository?

The skill first verifies configuration by calling `@codex review` and checking for an eyes reaction. If review is explicitly unavailable, it skips the loop, records the fallback evidence and head SHA, and runs runtime health checks and handoff for product-code PRs instead.

Can this skill handle pull requests across multiple branch layers?

Yes. It classifies changes as layer-0 common or project-layer, validates the PR target/base branch against that classification, and refuses to retarget project PRs to layer-0. Project PRs must come from task branches, never direct commits to the project main branch.

Why does the skill not trust the 'Didn't find any major issues' message alone?

Because pass phrases can coexist with unresolved inline comments on the current head. The skill cross-checks review bodies, inline comments by parent review commit, and call comments against the current head SHA before declaring the loop complete.

What are the timeout and retry limits in the review loop?

If no eyes reaction appears within 3 minutes of a call, the skill retries up to 3 times per head. After an eyes reaction, it waits up to 15 minutes for the Codex response before aborting with a timeout report requiring user judgment.