axtonliu

AI Pair Collaboration — AI skill for Claude Code

AI community intermediate

Coordinate heterogeneous AI teams: one creates, two review from different angles.

How to install AI Pair Collaboration

This entry records only its repository, not the path inside it, so there is no exact command to give. Open axtonliu/ai-pair and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What AI Pair Collaboration does

Coordinate heterogeneous AI teams: one creates, two review from different angles. Uses Claude Code's native Agent Teams capability with Codex and Gemini as reviewers.

When Claude uses AI Pair Collaboration

Trigger

/ai-pair, ai pair, dev-team, content-team, team-stop

Alternatives in AI

Codex Plugin — 's /codex:adversarial-review command 9.6k ★
Cumora — Where agent teams gather 3.2k ★
Omnara — by Ishaan Sehgal - A command center for AI agents that syncs Claude Code sessions across terminal, web, and mo 2.6k ★

README

name: ai-pair description: | AI Pair Collaboration Skill. Coordinate multiple AI models to work together: one creates (Author/Developer), two others review (Codex + Gemini). Works for code, articles, video scripts, and any creative task.

Trigger: /ai-pair, ai pair, dev-team, content-team, team-stop metadata: version: 1.5.0

AI Pair Collaboration

Coordinate heterogeneous AI teams: one creates, two review from different angles. Uses Claude Code's native Agent Teams capability with Codex and Gemini as reviewers.

Why Multiple AI Reviewers?

Different AI models have fundamentally different review tendencies. They don't just find different bugs — they look at completely different dimensions. Using reviewers from different model families maximizes coverage.

Commands

/ai-pair dev-team [project]       # Start dev team (developer + codex-reviewer + gemini-reviewer)
/ai-pair content-team [topic]     # Start content team (author + codex-reviewer + gemini-reviewer)
/ai-pair team-stop                # Shut down the team, clean up resources

Examples:

/ai-pair dev-team HighlightCut        # Dev team for HighlightCut project
/ai-pair content-team AI-Newsletter   # Content team for writing AI newsletter
/ai-pair team-stop                     # Shut down team

Prerequisites

Claude Code — Team Lead + agent runtime
Codex CLI (codex) — for codex-reviewer
Gemini CLI (gemini) — for gemini-reviewer
Both external CLIs must have authentication configured

Team Architecture

Dev Team (`/ai-pair dev-team [project]`)

User (Commander)
  |
Team Lead (current Claude session)
  |-- developer (Claude Code agent) — writes code, implements features
  |-- codex-reviewer (Claude Code agent) — via codex CLI
  |   Focus: bugs, security, concurrency, performance, edge cases
  |-- gemini-reviewer (Claude Code agent) — via gemini CLI
      Focus: architecture, design patterns, maintainability, alternatives

Content Team (`/ai-pair content-team [topic]`)

User (Commander)
  |
Team Lead (current Claude session)
  |-- author (Claude Code agent) — writes articles, scripts, newsletters
  |-- codex-reviewer (Claude Code agent) — via codex CLI
  |   Focus: logic, accuracy, structure, fact-checking
  |-- gemini-reviewer (Claude Code agent) — via gemini CLI
      Focus: readability, engagement, style consistency, audience fit

Workflow (Semi-Automatic)

Team Lead coordinates the following loop:

User assigns task → Team Lead sends to developer/author
Developer/author completes → Team Lead shows result to user
User approves for review → Team Lead sends to both reviewers in parallel

Reviewers report back → Team Lead consolidates and presents:

## Codex Review
{codex-reviewer feedback summary}

## Gemini Review
{gemini-reviewer feedback summary}

User decides → "Revise" (loop back to step 1) or "Pass" (next task or end)

The user