Coordinate Claude Code and Codex pair-programming with proposer/reviewer sign-offs.
npx skills add https://github.com/ccomkhj/skills --skill pair-coding
Please help me install this Agent Skill. Skill: pair-coding Source: https://github.com/ccomkhj/skills/tree/main/pair-coding Command: npx skills add https://github.com/ccomkhj/skills --skill pair-coding
It solves the problem of getting end-to-end, two-way accountability in code generation by forcing both Claude Code and Codex to propose and then review each other’s work at every stage.
.pair/ (PROGRESS, CONTEXT, DISCUSSION, SPEC/PLAN/STEP-N), so the loop is resumable and transparent.pair_handoff runs keep your terminal free, while pair_watch, pair_inject, and pair_takeover let you monitor or intervene safely.Use pair-coding when you want two AI agents to mutually review a coding task from spec through implemented steps in a single coordinated session.
High-intent search queries and answers about installing and using this skill.
Mutual code review between Claude Code and Codex is set up by enforcing alternating proposer and reviewer sign-offs for the spec, plan, and each code step, storing all shared workflow state and artifacts in a `.pair/` directory.
Yes, you can resume an interrupted pair-programming session because all session artifacts, progress, context, and disagreements are stored as resumable shared state in a `.pair/` working directory.
Cross-agent sign-off works by forcing both LLM agents to alternate as proposer and reviewer at every stage, gating progression to the next step only after the reviewing agent provides explicit sign-off on the current spec, plan, or code.
Disagreements between Claude and Codex are handled via a structured DISCUSSION log, allowing open disagreements to be tracked and resolved as decisions before being recorded as resolved context for future steps.
You can monitor or intervene in a detached coding workflow safely using file-based prompts, STATUS-driven handoffs, and specific commands like `pair_watch` to monitor, `pair_inject` to intervene, or `pair_takeover` to steer.
No external dependencies are required to coordinate Claude and Codex for two-way accountability, as the skill relies entirely on file-based artifacts and shared state within a local `.pair/` directory to manage the workflow.
adacosdevDetect tech stack and initialize Spec-Driven Development context for a project.
opsMachineGenerate a structured Test Plan from an approved spec by mapping acceptance criteria to test types.
rjmurilloMatch file paths against steering glob patterns and return prioritized steering files.
wtyler2505Delegate coding tasks to the Claude Code CLI for generation, refactoring, and reviews.