revdiff-plan

Featured

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response", "annotate codex output".

Code & Development 853 stars 90 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
98
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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: ```bash 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: ```bash 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 ##...

Details

Author
umputun
Repository
umputun/revdiff
Created
5 months ago
Last Updated
today
Language
Go
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

codex-plan-review

Cross-provider adversarial review of a finalized plan, spec, design doc, ADR, or code diff using OpenAI Codex (GPT-5.6 Terra). AUTO-TRIGGER at plan gates — invoke immediately after any of: (1) a plan written by `nightshift:plan` is finalized, (2) an ADR draft is completed. AUTO-TRIGGER for code: after implementing a Codex-reviewed plan, run diff mode on the branch range before opening the PR — a reviewed plan is NOT a reviewed diff. Also invoke on request — "codex review this plan", "codex review this diff", "get a second opinion on this design", "terra review". Do NOT re-run on an artifact already reviewed without an explicit user ask; each chain burns paid quota.

5 Updated 5 days ago
jasonm4130
Code & Development Listed

codex-plan-review

Send a design document to Codex CLI for review, then revise the document based on the findings. Automatically loops until no critical issues remain or 5 rounds are completed.

11 Updated 2 weeks ago
tykisgod
AI & Automation Listed

dev-review

Code-focused plan-bounce-execute workflow between Claude Code (Opus) and Codex CLI. Use when the user wants repo files changed, a bug fixed, a feature implemented, or a code plan verified before execution. One AI composes a plan, it bounces between agents with [CONTESTED]/[CLARIFY] markers until refined, then the designated agent executes the code. Replaces manual copy-paste between Claude Code and Codex desktops. Triggers on "dev review", "dev-review", "code review loop", "plan then execute", "have codex implement", "have codex review this diff", "developer reviewer loop", "compose execute verify", and explicit /dev-review requests. Generic co-evolution, bounce, cross-AI refinement, document refinement, and stress-test requests should use /co-evolution instead.

4 Updated yesterday
alanshurafa