codex-review

Address Codex pull request comments and audit the branch for repeated error patterns.

68|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/arjunrajlaboratory/mycelium --skill codex-review-arjunrajlaboratory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-review
Source: https://github.com/arjunrajlaboratory/mycelium/tree/main/skills/codex-review
Command: npx skills add https://github.com/arjunrajlaboratory/mycelium --skill codex-review-arjunrajlaboratory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codex review rounds on pull requests often loop: you fix the one flagged line, and Codex flags the same mistake elsewhere on the next pass. This Skill generalizes each Codex comment into an error pattern, sweeps the entire branch for other instances, fixes and tests them all, and drafts a reply so each review round actually converges. ## Core Features & Use Cases - Comment scoping and fetching: Locates the PR from a URL or the current branch, then collects open Codex comments across inline review comments, review summaries, and conversation comments using the GitHub CLI, identifying Codex by author login rather than bot type. - Pattern generalization and branch-wide audit: Converts each flagged line into a named error pattern (e.g., swallowed exceptions, hardcoded paths), diffs against the PR base ref, and searches the whole branch with grep/rg to fix every instance while guarding against false positives. - Verified, gated replies: Runs the project's tests and linters, drafts a per-comment reply summarizing fixes and audit tallies, gates the @codex review re-trigger on evidence of Codex access, and posts only after user confirmation. - Use Case: Codex flags a bare except: pass at one line of your PR. The skill fixes it, finds three more swallowed exceptions across the branch, runs pytest, and drafts a reply documenting the full audit for your approval. ## Quick Start Ask the assistant to address the Codex review comments on the current pull request and audit the whole branch for the same error patterns.

Frequently Asked Questions about codex-review

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

FAQPage Schema
How do I respond to Codex review comments on a pull request?

Fetch the open Codex comments with the GitHub CLI, generalize each into an error pattern, fix the flagged line, then audit the whole branch for the same pattern. Draft a reply summarizing fixes and audit results, and post it only after user confirmation.

How to find all instances of a bug pattern across a branch?

Diff the branch against the PR's base ref to scope changed files, then search with grep or ripgrep using a signature of the generalized mistake, such as `except.*:\s*pass` for swallowed exceptions. Reason about each hit to avoid rewriting correct lookalikes.

Does this work with pull requests targeting branches other than main?

Yes. The base ref is read from the PR's baseRefName, so PRs targeting develop, release, or master are diffed correctly using the remote-tracking ref. For local-only branches, the default branch is resolved from the remote instead of assuming main.

Why does @codex review not re-trigger a new review round?

Appending @codex review only works if the user has Codex access on the repository. The skill checks for evidence that the Codex bot previously reviewed the PR and asks the user before adding the trigger when no such evidence exists.

When should I not use this Codex review workflow?

Do not use it for a general code or scientific review with no Codex comment in play; use a general review skill instead. Also avoid force-fitting a fix when the Codex comment is wrong—reply with the reasoning instead.