codex-collab-review

Coordinates Claude and Codex CLI in tmux panes to produce consensus-based code reviews.

Updated May 20, 2026
One-click install
npx skills add https://github.com/TeXmeijin/agent-skills --skill codex-collab-review-texmeijin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-collab-review
Source: https://github.com/TeXmeijin/agent-skills/tree/main/.apm/skills/codex-collab-review
Command: npx skills add https://github.com/TeXmeijin/agent-skills --skill codex-collab-review-texmeijin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-reviewer code reviews miss issues and include false positives. This Skill runs Claude and Codex CLI as independent reviewers on the same diff, then reconciles their findings through structured discussion so only mutually agreed issues appear in the final review. ## Core Features & Use Cases - Independent parallel review: Claude and Codex review the same PR diff with the same review perspectives in separate tmux panes. - Consensus-based filtering: Findings from only one side are challenged through a discussion phase (max 2 rounds); only agreed issues are published, with unresolved ones listed in an appendix. - Structured final report: Outputs a Markdown review categorized into Critical, Warning, and Info, with the agreement process documented per finding. - Use Case: Given a PR URL, the Skill fetches the diff via gh, spawns Codex panes in tmux, cross-examines each side's unique findings, and produces a double-checked review report. ## Quick Start Ask the agent to run a collaborative review with Codex on a specific PR URL or branch name.

Frequently Asked Questions about codex-collab-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a collaborative code review with Claude and Codex CLI?

Provide a PR URL, branch name, or file path while inside a tmux session. The Skill fetches the diff with gh, launches Codex in separate tmux panes, runs independent reviews, then reconciles findings into a consensus report.

What tools are required for dual AI code review in tmux?

You need an active tmux session, the Codex CLI installed, and the GitHub CLI (gh) for fetching PR diffs. Large diffs over 20K lines fall back to git fetch and git diff.

Why does tmux send-keys fail to submit prompts to Codex?

Combining text and Enter in a single tmux send-keys call often fails to deliver Enter to Codex's interactive prompt. Always send the text and Enter as two separate send-keys commands, then verify with capture-pane.

How are disagreements between Claude and Codex review findings resolved?

Each disputed finding goes through a discussion phase with a maximum of two rounds. If no agreement is reached, the finding is moved to an appendix of unresolved items rather than the main review.

How many Codex panes should I use for large pull request reviews?

Use 1 pane for diffs up to 500 lines, 2 panes for 500-3000 lines, and 2-3 panes for larger diffs. Review perspectives are distributed across panes, with discussion consolidated into one pane.