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 the script directory using repo root first, then fall back to Codex home:

SCRIPT_DIR="$(git rev-parse --show-toplevel 2>/dev/null)/plugins/codex/skills/revdiff-plan/scripts"
if [ ! -d "$SCRIPT_DIR" ]; then
    SCRIPT_DIR="${CODEX_HOME:-$HOME/.codex}/skills/revdiff-plan/scripts"
fi

Also resolve the launcher script from the revdiff skill:

LAUNCHER_DIR="$(git rev-parse --show-toplevel 2>/dev/null)/plugins/codex/skills/revdiff/scripts"
if [ ! -d "$LAUNCHER_DIR" ]; then
    LAUNCHER_DIR="${CODEX_HOME:-$HOME/.codex}/skills/revdiff/scripts"
fi

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