Repository navigation
v0.2.0 — evidence-driven gates
This release makes the pair workflow prove more than “the tests passed.” Claude still
plans and reviews, Codex still implements in a pinned workspace sandbox, and the human
still decides what merges — but the green gate now demands stronger evidence.
Highlights
- Baseline-aware testing. Test counts are captured before the handoff, so a suite that
collects nothing or loses coverage cannot quietly read as green. - Test-diff integrity. Deleted or loosened assertions, new skips, tautological expected
values, and mocks that replace the behavior under test are explicit red gates. - Run it like a user. A fresh agent that has not read the implementation drives the
pre-agreed runtime scenarios and records commands, verbatim output, expectations, and
match or mismatch. - Safer installation and CI. Empty or root install destinations are refused; CI checks
the installer, skill frontmatter, opt-in guarantees, and repository-relative links.
git clone https://github.com/hyj28/claude-codex-pair.git
cd claude-codex-pair
./install.shThen invoke /pair, /pair fast, /pair strict, or /pair-review explicitly inside
Claude Code. Installing the skills does not change ordinary Claude Code or Codex behavior.
Read the complete workflow design
and changelog.