Revdiff Plan

revdiff-plan - Review Codex Output

Review the last Codex assistant message with inline annotations using revdiff TUI in a terminal overlay.

Script Path Resolution

Resolve <plugin-root> from this skill's absolute path in the available-skills catalogue. It is the directory containing this plugin's .codex-plugin/plugin.json. Then set:

SCRIPT_DIR="<plugin-root>/skills/revdiff-plan/scripts"

Also resolve the launcher script from the revdiff skill:

LAUNCHER_DIR="<plugin-root>/skills/revdiff/scripts"

Replace <plugin-root> with the resolved absolute path before running either command. Use $SCRIPT_DIR and $LAUNCHER_DIR in place of script paths throughout this skill.

Activation Triggers

• "revdiff-plan", "review plan with revdiff", "annotate plan"
• "review last response", "annotate codex output"

How It Works

1. Extract the last Codex assistant message from rollout files
2. Write it to a temp markdown file
3. Launch revdiff with --only=<tempfile> in a terminal overlay
4. User reads the plan, adds annotations on specific lines
5. On quit, annotations are captured from stdout
6. Codex reads annotations and addresses each one (refine plan, answer questions, fix issues)
7. Loop: re-launch revdiff to verify changes, user can add more annotations
8. Done when user quits without annotations; clean up temp file

Workflow

Step 1: Extract Last Assistant Message

Run the extraction script with --skip-current to avoid picking up this session's own output:

$SCRIPT_DIR/extract-last-message.sh --skip-current

The script:

• Uses a best-effort heuristic: picks the second most recent rollout JSONL file by modification time from ~/.codex/sessions/
• This assumes the newest file belongs to the active session; if concurrent Codex sessions exist, the wrong file may be selected
• Falls back to the newest file if only one session exists
• Extracts the last assistant message text using jq
• Outputs raw markdown to stdout
• Accepts an explicit rollout file path as an argument to bypass auto-detection when precision matters

If the script fails (no sessions, no messages), inform the user and stop. If the user reports that the wrong content was extracted, ask them to provide the rollout file path explicitly: $SCRIPT_DIR/extract-last-message.sh /path/to/rollout.jsonl

Capture the output and write it to a temp file:

TMPBASE="${TMPDIR:-/tmp}"
PLAN_FILE=$(mktemp "$TMPBASE/revdiff-plan-XXXXXX")
mv "$PLAN_FILE" "${PLAN_FILE}.md"
PLAN_FILE="${PLAN_FILE}.md"
$SCRIPT_DIR/extract-last-message.sh --skip-current > "$PLAN_FILE"

Step 2: Launch Review

Run the launcher script with --only=<tempfile>:

$LAUNCHER_DIR/launch-revdiff.sh --only="$PLAN_FILE"

The launcher sets REVDIFF_EXIT_CODE_ON_ANNOTATIONS; exit 10 means annotations were captured and is not a launcher failure. Treat other nonzero statuses as failures.

IMPORTANT -- long-running command: The launcher blocks until the user finishes reviewing in the TUI overlay. Set the bash timeout parameter to the maximum your harness allows (e.g. 1800000 or higher). Do NOT use run_in_background.

If the bash tool reports a timeout, use the same fallback as the revdiff skill:

1. Tell the user: "The bash tool timed out, but revdiff may still be open. Let me know when you're done reviewing."
2. Wait for the user to reply.
3. Read the most recent output file:

   output_file="$(ls -t "${TMPDIR:-/tmp}"/revdiff-output-* 2>/dev/null | head -1)"
   if [ -n "$output_file" ] && [ -f "$output_file" ]; then
     cat "$output_file"
   fi