Run any Skill in Manus with one click

codex-result

Stars48

Forks5

UpdatedJune 21, 2026 at 13:19

Show the final stored result of a completed Codex job. Use when asked "codex result", "show the codex output", "show me the job result", or wants output from a finished job.

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

LeeJuOh

LeeJuOh/claude-code-zero

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	codex-result
description	Show the final stored result of a completed Codex job. Use when asked "codex result", "show the codex output", "show me the job result", or wants output from a finished job.
argument-hint	[job-id]
allowed-tools	["Bash","Read","Glob"]

Codex Job Result + Stored Review Linking

Thin wrapper around the Official Codex companion's result subcommand. If a codex-advisor review file exists for the same timestamp window, also surface its path so the user can read the classified findings (Agreed / Disputed / Nuanced / False Positive / Uncited).

Phase 1: Fetch companion result

set -o pipefail
CODEX_COMPANION=$("${CLAUDE_PLUGIN_ROOT}/scripts/resolve-companion.sh") \
  || { echo "Official Codex plugin not found — run /codex-setup" >&2; exit 1; }

# Forward args verbatim. The companion accepts an optional [job-id];
# without one it shows the most recent finished job.
node "$CODEX_COMPANION" result $ARGUMENTS

Relay the companion's rendered result verbatim (includes the Codex session ID, making codex resume <session-id> possible).

Phase 2: Find the matching codex-advisor report

Codex-advisor stores reports at ${CLAUDE_PLUGIN_DATA}/reviews/<type>-<YYYYMMDD-HHMMSS>.md. These are separate from companion jobs — a given job may or may not have a matching report depending on which skill launched it.

REVIEWS_DIR="${CLAUDE_PLUGIN_DATA}/reviews"
if [ -d "$REVIEWS_DIR" ]; then
  # List the 3 most recent reports; the user can pick the one whose
  # timestamp aligns with the job.
  ls -1t "$REVIEWS_DIR" 2>/dev/null | head -3
fi

Append:

## Related codex-advisor reports (most recent)

- review-20260414-102530.md
- rescue-20260414-100112.md
- ...

If the timestamp matches the job you fetched, open that file for Claude's double-check classification. Path: ${CLAUDE_PLUGIN_DATA}/reviews/

Don't claim a specific report belongs to the queried job unless timestamps clearly align — the user decides.

Gotchas

The companion's result is authoritative for Codex output. codex-advisor's report adds classification on top but the raw Codex text lives in the companion's store.
No job-id → most recent. The companion picks the most recently completed job in the current workspace; this may not be what the user wants if they just finished multiple jobs. Prompt for clarification if ambiguous.
Session ID enables codex resume. If the companion's output includes a session_id, point that out — the user can continue that Codex thread with codex resume <session-id> outside Claude entirely.

More from this repository

same repository

worktree-setup

LeeJuOh/claude-code-zero

Set up worktree-plus for a repo — manage git config (baseBranch, branchPrefix, dirBase, guessRemote) and build the .worktreeinclude / .worktreelink files by scanning which gitignored files actually exist. Use when the user asks to set up or configure worktree-plus, view or change worktree settings, reset the plugin config, or decide which gitignored files should be copied or symlinked into new worktrees.

2026-07-1748

codex-rescue

LeeJuOh/claude-code-zero

Delegate an implementation task to Codex, then Claude reviews the result. Use when asked "codex rescue", "delegate to codex", "have codex do it", or wants Codex to implement or fix something.

2026-07-1748

codex-setup

LeeJuOh/claude-code-zero

Check Codex CLI, auth, Official plugin status, and configure defaults. Use when asked "codex setup", "configure codex", "install codex", or when another codex-advisor skill reports setup issues.

2026-07-1748

context-health-visual

LeeJuOh/claude-code-zero

Diagnose Claude Code environment health — context budget, description obesity, trigger collisions, hooks, MCP, plugins, CLAUDE.md, memory, and skill-security scan. Use when asked to audit the environment, check context budget, review plugins, or scan installed skills for risky patterns.

2026-07-1748

diff-visual

LeeJuOh/claude-code-zero

Visualize git diffs as interactive HTML reports with architecture diagrams, change analysis, and side-by-side split-diff of the actual changed code. Use when asked to visualize, review, or summarize a diff, branch, commit, or PR — including seeing the real changed lines, not just a summary. Accepts branch names, commit hashes, HEAD, PR numbers, or commit ranges.

2026-07-1748

doc-visual

LeeJuOh/claude-code-zero

Convert any markdown document into a diagram-enriched visual HTML report. Use when asked to visualize, illustrate, or create a visual report from a document with diagrams. Single md file input. Also trigger when: "make this document visual", "add diagrams to this doc", "turn this markdown into a report", "visualize this README/ADR/spec", or any request to render a document with embedded diagrams.

2026-07-1748

Codex Job Result + Stored Review Linking

Phase 1: Fetch companion result

set -o pipefail CODEX_COMPANION=$("${CLAUDE_PLUGIN_ROOT}/scripts/resolve-companion.sh") \ || { echo "Official Codex plugin not found — run /codex-setup" >&2; exit 1; } # Forward args verbatim. The companion accepts an optional [job-id]; # without one it shows the most recent finished job. node "$CODEX_COMPANION" result $ARGUMENTS

Relay the companion's rendered result verbatim (includes the Codex session ID, making codex resume <session-id> possible).

Phase 2: Find the matching codex-advisor report

REVIEWS_DIR="${CLAUDE_PLUGIN_DATA}/reviews" if [ -d "$REVIEWS_DIR" ]; then # List the 3 most recent reports; the user can pick the one whose # timestamp aligns with the job. ls -1t "$REVIEWS_DIR" 2>/dev/null | head -3 fi

Append:

## Related codex-advisor reports (most recent) - review-20260414-102530.md - rescue-20260414-100112.md - ... If the timestamp matches the job you fetched, open that file for Claude's double-check classification. Path: ${CLAUDE_PLUGIN_DATA}/reviews/

Don't claim a specific report belongs to the queried job unless timestamps clearly align — the user decides.

Gotchas

The companion's result is authoritative for Codex output. codex-advisor's report adds classification on top but the raw Codex text lives in the companion's store.

No job-id → most recent. The companion picks the most recently completed job in the current workspace; this may not be what the user wants if they just finished multiple jobs. Prompt for clarification if ambiguous.

Session ID enables codex resume. If the companion's output includes a session_id, point that out — the user can continue that Codex thread with codex resume <session-id> outside Claude entirely.