cross-llm-pair-review

Coordinate Codex and Claude to review code changes before commit.

2|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Canhada-Labs/ceo-orchestration --skill cross-llm-pair-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-llm-pair-review
Source: https://github.com/Canhada-Labs/ceo-orchestration/tree/main/.claude/skills/core/cross-llm-pair-review
Command: npx skills add https://github.com/Canhada-Labs/ceo-orchestration --skill cross-llm-pair-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codex, claude, adr-052, adr-105, adr-106, adr-107, adr-108, adr-111, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures code quality and compliance by implementing a cross-LLM (Codex and Claude) review process, preventing unreviewed and irreversible changes.

Core Features & Use Cases

  • Cross-LLM Review: Combines Codex and Claude to review changes before they are committed, reducing the risk of errors.
  • Audit Logging: Provides a tamper-evident audit log of all agent spawns, edits, and ceremonies for traceability.
  • Review Rail: Allows a second LLM (Codex) to review Claude's edits to protected paths before they are applied.
  • Skill Checklists: Offers ready-made skill checklists for agents to load on demand.

Quick Start

Activate the cross-llm-pair-review skill with the command: .claude/scripts/inject-agent-context.sh --pair-mode --coder=codex --reviewer=claude

Frequently Asked Questions about cross-llm-pair-review

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

FAQPage Schema
How does cross-LLM code review improve compliance and safety?

Cross-LLM code review improves compliance by coordinating Codex and Claude models to evaluate changes before commits, enforcing ADR governance policies and preventing unreviewed or irreversible edits to protected paths.

How do I set up a cross-LLM review process between Codex and Claude?

Set up cross-LLM review by running the inject-agent-context.sh script with pair-mode flags, designating Codex as the coder and Claude as the reviewer to evaluate edits before application.

Can I use audit logging to trace LLM agent edits and spawns?

Audit logging provides a tamper-evident record of all agent spawns, edits, and ceremonies, ensuring full traceability for compliance and governance in software development workflows.

What is a review rail and how does it protect code paths?

A review rail protects code paths by requiring a second LLM, such as Codex, to review and approve edits made by Claude to protected paths before any changes are applied, preventing irreversible modifications.

Do I need specific ADRs configured to enforce LLM governance policies?

Yes, this process requires specific ADRs (adr-052, adr-105, adr-106, adr-107, adr-108, adr-111) to enforce governance policies, validate rubric violations, and coordinate the cross-LLM review workflow effectively.

What are the limitations of using multiple LLMs for code review?

The limitation of using multiple LLMs for code review is the strict dependency on coordinating both Codex and Claude models, alongside specific ADR configurations, which restricts use in environments lacking these exact dependencies.