Run any Skill in Manus with one click

codex-review

Stars0

Forks0

UpdatedJuly 6, 2026 at 18:29

Independent second-pass code review from Codex (GPT-5.x). Use when the user wants a second opinion on uncommitted changes, a branch diff, a commit, or a PR, or when a change is broad enough that another agent's perspective is useful before merging.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

SunkenInTime

SunkenInTime/my-conf

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	codex-review
description	Independent second-pass code review from Codex (GPT-5.x). Use when the user wants a second opinion on uncommitted changes, a branch diff, a commit, or a PR, or when a change is broad enough that another agent's perspective is useful before merging.

Codex as independent reviewer

Codex is a different model family with different blind spots — that independence is the whole value. Its report is evidence, not verdict: you verify before you relay.

Command mechanics (flags, sandbox, resume) live in the shared wrapper's docs: C:\Users\shawn\.claude\skills\codex\SKILL.md.

Steps

Identify the review target. One of: uncommitted changes, a branch diff against a named base, a specific commit, or a PR. Done when you can state it as a single unambiguous git ref or range.
Create a temporary artifact directory for the Codex report (e.g. mktemp -d), so the report survives for inspection and never lands in the repo. Done when the directory exists outside the working tree.
Run the review read-only via the wrapper, telling Codex to write its full report to the artifact directory:
```
node C:\Users\shawn\.claude\skills\codex\scripts\codex-run.mjs --read --cd <repo> \
  "Review <target>. Focus on <the one or two things that matter for this change>. Write your full report to <artifact-dir>/report.md."
```
Prompt Codex simply — it is not Claude. State the target, the focus, and where to put the report; skip elaborate role-play and long constraint lists. Done when the run exits and the report exists.
Verify the important claims against the code before presenting them. Open the files Codex cites and confirm each finding you intend to relay; drop or explicitly flag anything you can't confirm. Done when every finding in your summary has been checked in-source.
Report. If Codex found nothing, say that clearly and name the exact target it inspected — never silently rerun. Done when the user has either verified findings or an explicit clean bill for a named target.

More from this repository

same repository

blip-to-phone

SunkenInTime/my-conf

Delegate a Blip file transfer to Codex computer use. Use when the user asks Claude to send, blip, transfer, move, or copy a local file to their phone with Blip; the recipient must be exactly Galaxy S21 Ultra 5G.

2026-07-060

codex-computer-use

SunkenInTime/my-conf

Codex (GPT-5.x) computer-use verification — drives the browser or desktop, launches apps, captures screenshots. Use when the user asks to test a flow, verify UI behavior, inspect a running app, capture screenshots, or confirm implemented behavior end-to-end.

2026-07-060

codex-implementation

SunkenInTime/my-conf

Delegate bounded implementation work to Codex (GPT-5.x) — clear-spec features, migrations, bulk mechanical edits. Use when a task is well-specified enough to hand off whole and worth doing on Codex's near-free usage instead of Claude's, usually in a worktree.

2026-07-060

codex

SunkenInTime/my-conf

Drive OpenAI Codex from Claude Code — raw wrapper mechanics for prompts, structured JSON, image generation, and session resume. Use when the user wants to "ask Codex" or delegate a task that codex-review, codex-implementation, and codex-computer-use don't cover; those skills point here for command mechanics.

2026-07-060

wrec-screen-recording

SunkenInTime/my-conf

Record the screen with wrec. Use when the user wants a screen recording, sample video, display/window/app capture, system-audio capture, cursor or Wrec-window visibility control, recording job control, output lookup, or wrec CLI usage.

2026-07-060

blip-to-phone

SunkenInTime/my-conf

Blip a local file to Shawn's phone. Use when the user asks to send, blip, transfer, move, or copy an APK or other local file to their phone with Blip; the recipient must be exactly Galaxy S21 Ultra 5G and the transfer must be visually verified.

2026-07-060

name	codex-review
description	Independent second-pass code review from Codex (GPT-5.x). Use when the user wants a second opinion on uncommitted changes, a branch diff, a commit, or a PR, or when a change is broad enough that another agent's perspective is useful before merging.

Codex as independent reviewer

Codex is a different model family with different blind spots — that independence is the whole value. Its report is evidence, not verdict: you verify before you relay.

Command mechanics (flags, sandbox, resume) live in the shared wrapper's docs: C:\Users\shawn\.claude\skills\codex\SKILL.md.

Steps

Identify the review target. One of: uncommitted changes, a branch diff against a named base, a specific commit, or a PR. Done when you can state it as a single unambiguous git ref or range.
Create a temporary artifact directory for the Codex report (e.g. mktemp -d), so the report survives for inspection and never lands in the repo. Done when the directory exists outside the working tree.
Run the review read-only via the wrapper, telling Codex to write its full report to the artifact directory:
```
node C:\Users\shawn\.claude\skills\codex\scripts\codex-run.mjs --read --cd <repo> \
  "Review <target>. Focus on <the one or two things that matter for this change>. Write your full report to <artifact-dir>/report.md."
```
Prompt Codex simply — it is not Claude. State the target, the focus, and where to put the report; skip elaborate role-play and long constraint lists. Done when the run exits and the report exists.
Verify the important claims against the code before presenting them. Open the files Codex cites and confirm each finding you intend to relay; drop or explicitly flag anything you can't confirm. Done when every finding in your summary has been checked in-source.
Report. If Codex found nothing, say that clearly and name the exact target it inspected — never silently rerun. Done when the user has either verified findings or an explicit clean bill for a named target.