The user invokes you like: $claude-review <jobId-or-prefix>. The first token after $claude-review is the job id (or a job-id prefix). If the user does not provide a job id, ask for it before running.
Resolve <plugin-root> as the parent directory of the skills/ directory that contains this file (so <plugin-root>/scripts/cc.mjs is the dispatcher). Confirm <plugin-root>/scripts/cc.mjs exists before running.
Run the dispatcher:
```
node "<plugin-root>/scripts/cc.mjs" review <jobId-or-prefix> [flags]
```
Forward only these flags when the user explicitly requests them: --all, --json, --yes, --blocking, --fail-on. Do NOT forward --allow-edit, --model, --effort, --permission-mode, --add-dir, --mcp-config, --name, or other fresh-session startup flags — they are not applicable to this subcommand. Do NOT inject --yes automatically. If the dispatcher reports that an acknowledgement is required, surface that message to the user instead of retrying with --yes.
Return the dispatcher's stdout verbatim. If the command exits non-zero, surface stdout and stderr to the user and explain that the dispatcher failed. Do not reimplement the command logic yourself.

This skill sends an additional prompt through Claude Code and may count toward your Claude Code usage.

Note: By default, the review evaluates the latest completed non-review turn. Reviewing a review is allowed but not recommended; use a future explicit turn-selection feature if you need that workflow.

Next steps

After a lightweight review, the user typically wants one of:

$claude-adversarial-review — get an independent second-opinion review
$claude-result — re-read the original job output

Más de este repositorio

mismo repositorio

claude-doctor

wu-hongjun/cc-plugin-codex

Preflight Claude Code auth, model access, real-browser readiness, workspace path, and permission mode before long delegated jobs.

2026-06-242

claude-status

wu-hongjun/cc-plugin-codex

List Claude jobs for the current workspace.

2026-06-242

claude-upgrade

wu-hongjun/cc-plugin-codex

Refresh or repair the installed CC Codex plugin through Codex plugin commands.

2026-06-242

claude-wait

wu-hongjun/cc-plugin-codex

Wait for a Claude job to produce a result, blocker, or timeout.

2026-06-242

claude-adversarial-review

wu-hongjun/cc-plugin-codex

Run an adversarial code review of a Claude job in a fresh independent Claude Code session (thorough; eliminates confirmation bias).

2026-06-242

claude-batch

wu-hongjun/cc-plugin-codex

Run a batch of Claude Code instructions via the Batch Parallel Work Orchestration runtime.

2026-06-242

name	claude-review
description	Review the output of a Claude job by reusing its existing Claude Code session (lightweight; same-session).

You are the Codex skill wrapper for sending a structured review turn to an existing Claude background job created by $claude-delegate.

The user invokes you like: $claude-review <jobId-or-prefix>. The first token after $claude-review is the job id (or a job-id prefix). If the user does not provide a job id, ask for it before running.
Resolve <plugin-root> as the parent directory of the skills/ directory that contains this file (so <plugin-root>/scripts/cc.mjs is the dispatcher). Confirm <plugin-root>/scripts/cc.mjs exists before running.
Run the dispatcher:
```
node "<plugin-root>/scripts/cc.mjs" review <jobId-or-prefix> [flags]
```
Forward only these flags when the user explicitly requests them: --all, --json, --yes, --blocking, --fail-on. Do NOT forward --allow-edit, --model, --effort, --permission-mode, --add-dir, --mcp-config, --name, or other fresh-session startup flags — they are not applicable to this subcommand. Do NOT inject --yes automatically. If the dispatcher reports that an acknowledgement is required, surface that message to the user instead of retrying with --yes.
Return the dispatcher's stdout verbatim. If the command exits non-zero, surface stdout and stderr to the user and explain that the dispatcher failed. Do not reimplement the command logic yourself.

This skill sends an additional prompt through Claude Code and may count toward your Claude Code usage.

Note: By default, the review evaluates the latest completed non-review turn. Reviewing a review is allowed but not recommended; use a future explicit turn-selection feature if you need that workflow.

Next steps

After a lightweight review, the user typically wants one of:

$claude-adversarial-review — get an independent second-opinion review
$claude-result — re-read the original job output