crosschecklisted

Use in Claude when the user wants Claude↔Codex cross-verification ping-pong — both analyze independently (blind), exchange findings, merge conclusions, the host implements, and the counterpart checks completion. On this Claude entrypoint, Claude is the host and Codex is the reviewer. Supports analyze-only / plan-only / full / verify-only. Triggers — "크로스체크", "codex 교차검증", "코덱스랑 핑퐁", "codex 리뷰 받아", "교차검증하고 작업해", "codex한테 물어봐", "둘이 의견 취합해", and the English equivalents "crosscheck", "cross-check with codex", "ping-pong with codex", "get a codex review", "ask codex", "have codex verify this", "merge both opinions", "/crosscheck". Korean and English triggers are equivalent; reply in whichever language the user writes. Every Codex call goes through scripts/codex_ask.sh; never call codex exec directly or paste file contents or diffs into prompts.
moveju112/skill_verify · ★ 1 · AI & Automation · score 72

Install: claude install-skill moveju112/skill_verify

# Claude-hosted Crosscheck (crosscheck) > Response language — follow the language the user writes in. Korean request, report in Korean; English request, report in English. > This rule document is written in English; that has no bearing on the language of the output delivered to the user. Claude and Codex each **analyze independently**, then exchange and merge results. The agent running the user session owns implementation; the counterpart is an independent analyst and verifier. **In this Claude entrypoint, Claude implements and Codex reviews.** The Codex entrypoint uses the reciprocal flow in `platforms/codex/verify`. ## Modes — infer from the request; when ambiguous, use full | Mode | Trigger examples | Phases run | |---|---|---| | `analyze` | "둘이 의견 취합해줘", "교차 분석만" / "just cross-analyze", "merge both opinions only" | A | | `plan` | "핑퐁해서 계획만 줘", "계획서 뽑아" / "ping-pong a plan only", "plan but do not implement" | A + B | | `full` (default) | "교차검증하고 작업해" / "cross-check it and do the work" | A + B + C + D | | `verify` | "다 됐는지 codex 체크", "이 변경 검증해" / "have codex check it is done", "verify this change" | D | - Trigger examples are illustrative, not exhaustive; Korean and English phrasings are equivalent. Match on intent, not wording. - Before falling back to `full`, check whether the request excludes implementation ('analysis only', 'plan only', 'don't change code'). Only default to `full` when implementation is genuinely implied. - Phases combine freely. If the user stop