Menu
Spawn codex as an independent external reviewer in a new tmux window. Codex performs a general PR review and publishes findings back via hive messaging. Use standalone for an external second opinion, or alongside /review to run both concurrently.
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.
Based on SOC occupation classification
Best practices for working with Go codebases. Use when writing, debugging, or exploring Go code, including reading dependency sources and documentation.
Autonomous orchestration loop for hive hc tasks. The high-capability manager model reads pending tasks, delegates implementation to cheaper worker sub-agents, critically reviews their output, and commits only code that passes quality checks. Runs to completion without stopping to ask questions.
Post-implementation design re-evaluation. After a feature reaches a working state through iteration, step back and re-examine what actually got built: are the data structures and algorithms the right fit for the access patterns that emerged, can code paths that grew through iteration be consolidated, and what iteration residue (tests for abandoned designs, dead flags/scaffolding, debug logging) should be deleted. Produces a tiered proposal report and applies only approved changes. Use when the user says "rethink this", "step back and re-evaluate", "is this the right design/data structure", "apply CS fundamentals", or wants a design pass on a working feature branch before PR. Not for bug-hunting (/review) or expression-level polish (/simplify) — this questions the design those skills preserve.
Orchestrate parallel claude and codex CLI agents through tmux to deliver a feature end-to-end. The orchestrator delegates planning, work, and review to spawned agents in tmux windows; it does NOT write or edit code itself. User-invoked only.
Open the current branch's diff (or a specific PR) in Plannotator's browser-based code review UI and act on the returned feedback. Use when the user says "review my changes in plannotator", "open the diff for review", "review this PR in plannotator", "let me annotate the diff", or returns to a session to gate code the agent produced.
Single-pass code review of the current branch (or a diff) that routes the changes to relevant concerns, dispatches fresh-context reviewer sub-agents, verifies findings to strip false positives, and reports a ranked, evidence-backed review. Use when the user asks to review local changes, a branch, or a PR before it goes to humans.
| name | review-with-codex |
| description | Spawn codex as an independent external reviewer in a new tmux window. Codex performs a general PR review and publishes findings back via hive messaging. Use standalone for an external second opinion, or alongside /review to run both concurrently. |
| allowed-tools | Bash(tmux:*),Bash(hive msg:*),Bash(hive session:*),Bash(git:*),Bash(mktemp:*),Bash(chmod:*),Bash(printf:*),Bash(rm:*) |
| disable-model-invocation | true |
| argument-hint | [base-branch] |
Spawn codex as an independent external reviewer in a new tmux window. Codex reviews the current branch and publishes its findings back to this session via hive messaging.
Default base branch: main. If an argument is provided, use it instead.
Check that the session is running inside tmux. If not, fail immediately with a clear error.
if [ -z "$TMUX" ]; then
echo "Error: review-with-codex requires a tmux session. Not currently in tmux."
exit 1
fi
git branch --show-current # current branch name
git diff <base-branch>...HEAD --stat # scope of changes
hive session info --json # get session ID
REVIEW_TOPIC=$(hive msg topic --prefix "review")
Save this value. Codex will publish findings to <REVIEW_TOPIC>.codex. You will subscribe
to that topic in Step 4.
Write a self-contained shell script to a tempfile and execute it in a new tmux window. Using a tempfile avoids quoting problems when embedding a multi-line prompt.
REVIEW_TOPIC=<from-step-2>
BASE_BRANCH=<base-branch>
REPO_PATH=$(pwd)
BRANCH=$(git branch --show-current)
SCRIPT=$(mktemp /tmp/codex-review-XXXXXX.sh)
chmod +x "$SCRIPT"
printf '#!/bin/bash\ncd %q && codex %q\n' "$REPO_PATH" "You are performing an independent code review of branch: $BRANCH
Your workflow:
1. Review all changes against $BASE_BRANCH:
git diff $BASE_BRANCH...HEAD
git diff
2. Analyse for issues including but not limited to: logic bugs, error handling, edge cases,
race conditions, resource leaks, security vulnerabilities, naming problems, design issues,
and test coverage gaps. You are a general reviewer — be thorough across all dimensions.
3. YOU MUST publish your findings before exiting. Run this exact command:
hive msg pub --topic $REVIEW_TOPIC.codex \"your detailed findings\"
This is not optional. The session that dispatched you is blocked waiting for this message.
Do not summarise to stdout and stop. Do not skip this step." > "$SCRIPT"
tmux new-window -n "review-codex" "$SCRIPT"
This returns immediately. Codex runs asynchronously in the new window.
Block until codex publishes its findings (up to 1 hour):
hive msg sub --topic <REVIEW_TOPIC>.codex --wait --timeout 1h
The output is codex's full review. Capture it for synthesis.
Read the diff directly to verify and contextualise codex's findings:
git diff <base-branch>...HEAD
git diff
Then produce a review report:
review skill (Step 5) for structureWhen using both skills together, run them so codex and Claude's internal sub-agents execute concurrently. The pattern:
Step 2 of review (before dispatching sub-agents): Run Steps 0–3 of this skill to spawn codex in tmux. This is non-blocking — codex starts immediately in the background.
Step 3 of review: Dispatch internal sub-agents in parallel as normal. They run concurrently with codex.
Step 4 of review: After internal sub-agents complete, run Step 4 of this skill
(hive msg sub --wait) to collect codex's findings. By this point codex may already be
done, so the wait is often short.
Synthesis: Merge all findings — internal sub-agents + codex — into a single report. Add a section identifying which issues were caught only by the external reviewer:
### External Review (Codex)
[Issues caught by codex that internal review missed, or where codex's independent
perspective adds confidence. Note any contradictions with internal findings.]
Include all findings in the unified Critical / Suggestions / Nits ranking.