skills.rest
ccomkhj
ccomkhjCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

run-pair-coding

Validate Claude Code and Codex pair-coding protocol transitions end-to-end.

8|1|Updated Feb 22, 2026
Search Tags:#Codex#Claude Code#pair programming#smoke test#repo automation#CLI verification#protocol state machine
One-click install
npx skills add https://github.com/ccomkhj/skills --skill run-pair-coding
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-pair-coding
Source: https://github.com/ccomkhj/skills/tree/main/pair-coding/.claude/skills/run-pair-coding
Command: npx skills add https://github.com/ccomkhj/skills --skill run-pair-coding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Verify that the pair-coding skill still functions correctly after changes by running a real, authenticated Claude Code ↔ Codex round-trip and checking the expected .pair protocol transitions.

Core Features & Use Cases

  • End-to-end protocol validation: Launches codex against a throwaway repo with pre-staged .pair/CONTEXT.md, .pair/PROGRESS.md, .pair/DISCUSSION.md, and .pair/SPEC.md, then verifies STATUS, TURN, and spec sign-off.
  • Fast iteration mode: Runs a no-LLM lint check that confirms the parent SKILL.md frontmatter and that codex/claude CLIs are available on PATH.
  • Debug-friendly artifacts: Writes turn logs under /tmp and intentionally leaves the test directory for inspection when failures occur.

Quick Start

Run the smoke test by giving the command: ./smoke.sh --smoke from the run-pair-coding skill directory.

Frequently Asked Questions about run-pair-coding

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

FAQPage Schema
How do I smoke-test a Claude Code and Codex pair programming workflow?▼

Smoke-test the pair programming workflow by running ./smoke.sh --smoke to execute a real Claude Code and Codex round-trip against a throwaway repository and verify .pair protocol transitions.

What does the pair-coding protocol state machine verify during an end-to-end test?▼

The protocol state machine verification checks expected .pair protocol transitions by validating PROGRESS.md STATUS, TURN values, and spec sign-off after the Codex execution completes.

Can I run a fast lint check for pair-coding without sending requests to an LLM?▼

You can run a fast no-LLM lint check that confirms the parent SKILL.md frontmatter is valid and verifies codex and claude CLIs are available on your PATH.

Where does the pair-coding smoke test write debug artifacts when failures occur?▼

The smoke test writes turn logs under /tmp and intentionally leaves the test directory intact for manual inspection when failures occur.

Do I need a specific repository setup to verify the Codex CLI coordination protocol?▼

Yes, the verification requires an SKILL.md with valid name and description frontmatter, and it stages pre-configured .pair/CONTEXT.md, PROGRESS.md, DISCUSSION.md, and SPEC.md files in a throwaway repository under /tmp.

Why does my pair-coding protocol validation fail after repo automation changes?▼

Protocol validation fails after repo automation changes when the codex exec execution with workspace-write does not produce the correct STATUS, TURN, or spec sign-off expected by the state machine.

Related Skills

Explore More Software Engineering Skills→
xiongxianfeixiongxianfei
3

codex-install-only

Document the Codex install location under .codex/skills for runtime configuration.

Community
Basic
timzaaktimzaak
64

t-demo-run

Run a single demo E2E test, diagnose failures, and dispatch fixes until it passes.

Community
Advanced
wentoraiwentorai
850

codex-cli

Delegate coding and debugging tasks to OpenAI Codex CLI.

Community
Advanced
rafasoaresrafasoares

playwright-cli

Automate browser interactions and end-to-end testing workflows with the Playwright CLI.

Community
Advanced