pr-codex-resolve

Reply to codex review comments and resolve threads after fixes are pushed.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ebijun1007/vibe-coding --skill pr-codex-resolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-codex-resolve
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.claude/skills/pr-codex-resolve
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill pr-codex-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automatically replies to codex review comments on a PR with the corrected changes and then resolves the corresponding review thread. It focuses only on unresolved threads tied to code lines, ignoring top-level issue comments.

Core Features & Use Cases

  • Detects unresolved codex review threads and associates them with the PR on the current branch.
  • After pushing fixes, posts a reply containing the fix summary and then resolves the thread.
  • Validates the author of the review and enforces guardrails to avoid accidental closure of non-target threads.

Quick Start

Push fixes to your PR, then run this skill to reply to codex review comments and automatically resolve the thread.

Frequently Asked Questions about pr-codex-resolve

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

FAQPage Schema
How do I automatically resolve codex review threads on a pull request after pushing fixes?

You can automatically resolve codex review threads by running a skill that detects unresolved threads on the current branch PR, replies with a fix summary, and closes the thread using GitHub CLI and GraphQL after fixes are pushed.

What is the process for replying to bot review comments on a PR and closing the thread?

Replying to bot review comments involves filtering unresolved threads linked to code lines, validating the target authors like codex or bot accounts, posting a reply with the corrected changes, and then resolving the corresponding thread.

Does the GitHub codex review thread resolver require authentication to close comments?

Yes, the codex review thread resolver requires authentication to operate. It uses GitHub CLI and GraphQL to map threads to commits and enforces explicit safeguards to prevent accidental closure of non-target threads.

Can I use this automation to close top-level issue comments on a GitHub pull request?

No, this automation focuses only on unresolved review threads tied to code lines. It explicitly ignores top-level issue comments to ensure only specific code review feedback from target authors is resolved.

What safeguards prevent accidental closure of non-target review threads on GitHub?

Safeguards include validating the author of the review thread to ensure it belongs to codex or bot accounts, and only closing threads after a successful reply is posted, which prevents accidental closure of non-target threads.