codex-collab

Coordinates independent peer review of primary analysis with evidence verification and synthesis.

5|9|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ajenchen/design-system --skill codex-collab-ajenchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-collab
Source: https://github.com/ajenchen/design-system/tree/main/.agents/skills/codex-collab
Command: npx skills add https://github.com/ajenchen/design-system --skill codex-collab-ajenchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-provider AI analysis can contain blind spots, unverified claims, or missed counterexamples. This Skill enforces a governance workflow where a primary analysis is independently reviewed by a genuinely different provider, with strict evidence, isolation, and immutability requirements before conclusions are synthesized. ## Core Features & Use Cases - Independent Peer Review: Dispatches an identical evidence-complete brief to a different provider running in a separate, read-only context. - Evidence Verification: Verifies peer claims against primary evidence, preserves disagreements, and synthesizes only supported conclusions. - Strict Blocking Rules: Returns REVIEW-BLOCKED when transport, identity, isolation, coverage, or worktree integrity cannot be proven. - Use Case: Before merging a high-stakes governance change, run the primary analysis, then have an independent provider review the same frozen brief and evidence digests, and synthesize only mutually supported findings. ## Quick Start Run an independent peer review of my current analysis using the codex-collab workflow and synthesize the verified findings.

Frequently Asked Questions about codex-collab

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

FAQPage Schema
How do I run an independent peer review of an AI analysis?

Complete the primary analysis first, then dispatch the same frozen evidence-complete brief to a genuinely different provider in a separate read-only context. Verify the peer's claims against the primary evidence and synthesize only mutually supported conclusions.

What makes a peer review provider count as independent?

The peer must be a different registered provider running in a separate context with read-only access via an immutable snapshot or enforced write denial. A same-provider worker, renamed command, or prompt variation does not qualify as independent evidence.

When does the review return REVIEW-BLOCKED?

REVIEW-BLOCKED is returned when transport is unavailable, the same provider is used, identity or evidence is missing, coverage is incomplete, isolation is absent, or worktree drift is detected. It is never converted into a PASS.

Can the peer reviewer modify the workspace during review?

No. The peer review is strictly read-only, enforced through an immutable snapshot or tool-level write denial. Before-and-after worktree fingerprinting detects any mutation, and detected drift blocks the review.

What evidence must be recorded for a peer review?

The artifact record includes primary and peer provider IDs, transport binding, brief, inventory, rubric, and response digests, read-only confirmation, and start and end timestamps. Credentials are never persisted.