cr

Coordinate cross-model code reviews between Claude and Codex with structured P1/P2/P3 reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fancive/claude-skills --skill cr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cr
Source: https://github.com/fancive/claude-skills/tree/main/skills/cr
Command: npx skills add https://github.com/fancive/claude-skills --skill cr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cross-model code review coordinates feedback between Claude Code and Codex to surface alternative perspectives and improve code quality across diffs.

Core Features & Use Cases

  • Two-way reviews: Claude reviews changes in Codex environment and Codex reviews Claude-generated diffs to increase accuracy and coverage.
  • Automated workflow: Handles changelog auto-generation, file staging, lint, and structured P1/P2/P3 reporting.
  • Use Case: When you need a second opinion on a critical diff or want consistent reviews across tools.

Quick Start

Say /cr to start a cross-model review of your current diff and let Claude and Codex provide a combined assessment.

Frequently Asked Questions about cr

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

FAQPage Schema
What is cross-model code review and when do I need it?

Cross-model code review coordinates feedback between Claude and Codex to surface alternative perspectives. You need it when you want a second opinion on critical diffs or require consistent reviews across different CLI environments to increase accuracy and coverage.

How do I get a second opinion on a code diff using Claude and Codex?

To get a second opinion on a code diff, you can initiate a two-way review where Claude reviews changes in the Codex environment and Codex reviews Claude-generated diffs. This process surfaces alternative perspectives to improve code quality across your changes.

Does cross-model code review auto-generate changelogs and run lint checks?

Yes, cross-model code review handles automated workflows including changelog auto-generation, file staging, and lint checks. It produces a structured P1/P2/P3 report to organize the feedback and improve code quality across diffs.

Can I use cross-model code review in both Claude Code and Codex CLI environments?

Yes, you can apply cross-model code review to code changes and diffs in both Claude Code and Codex CLI environments. This enables paired reviews for critical changes and allows each model to review the other's generated diffs.

What is the best way to run paired code reviews for critical changes?

The best way to run paired reviews for critical changes is coordinating cross-model feedback between Claude and Codex. This automated workflow stages files, runs lint checks, auto-generates changelogs, and produces a structured P1/P2/P3 report.

How do I start a cross-model code review of my current diff?

To start a cross-model code review of your current diff, you can use the /cr command. This triggers an agent workflow where Claude and Codex provide a combined assessment by auto-generating changelogs and running lint checks.