Multi Agent Verify
Multi-agent parallel verification. Spawns 3 independent agents (OpenCode CLI, Codex CLI, Claude Task subagent) in separate git worktrees to review, test, and fix code. Synthesizes results and applies final fixes on the original branch.
Install
npx skills add leyuan0602-glitch/cc-claude-codex --skill multi-agent-verifygit clone --depth 1 https://github.com/leyuan0602-glitch/cc-claude-codex.git /tmp/cc-claude-codex
mkdir -p ~/.claude/skills
cp -r /tmp/cc-claude-codex/multi-agent-verify ~/.claude/skills/multi-agent-verifyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Multi-Agent Verify: Parallel Verification with 3 Independent Agents You are the Main Agent (Claude Code). You orchestrate 3 independent agents to verify code in parallel. Each agent works in its own git worktree, reviews code, writes tests, runs verification, and fixes bugs independently. You then synthesize their findings and apply a final fix. ## Agent Launch Methods Each agent uses a DIFFERENT launch mechanism: | Agent | Method | Why | |-------|--------|-----| | **OpenCode** | `Bash` CLI: `opencode run -m opencode/minimax-m2.5-free "..."` | External CLI, free model, no nesting issues | | **Codex** | `Bash` CLI: `codex exec --full-auto "..."` | External CLI, no nesting issues | | **Claude** | `Task` tool with `isolation: "worktree"` | MUST use Task tool — `claude` CLI CANNOT run nested inside Claude Code (detects `CLAUDECODE` env var and refuses) | **CRITICAL**: Never launch `claude` via Bash CLI from within Claude Code. Always use the Task tool with `isolation: "worktree"` and `run_in_background: true`. ## Prerequisites Before invoking: 1. All code changes are committed on the current branch 2. Requirements are available (from `status.md` or conversation context) 3. `opencode` and `codex` are in PATH (check with `which`) 4. No external orchestrator script is required — launch agents directly ## Phase V1: Preparation ### Mode A: cc-claude-codex Integration When called as cc-claude-codex Phase 3:
Details
- Skill name
multi-agent-verify- Repository
- leyuan0602-glitch/cc-claude-codex
- Path
multi-agent-verify/SKILL.md- License
- MIT
- Repo updated
- 2 March 2026
FAQ
What does the Multi Agent Verify skill do?
Multi-agent parallel verification. Spawns 3 independent agents (OpenCode CLI, Codex CLI, Claude Task subagent) in separate git worktrees to review, test, and fix code. Synthesizes results and applies final fixes on the original branch.
How do I install the Multi Agent Verify skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add leyuan0602-glitch/cc-claude-codex --skill multi-agent-verify. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Multi Agent Verify popular?
It lives in leyuan0602-glitch/cc-claude-codex, which has 9 GitHub stars and 2 forks.
Related skills
Cc Claude Codex
9leyuan0602-glitch/cc-claude-codex
Development skill where Claude Code acts as supervisor and Codex acts as executor. Auto-trigger for implementation, debugging, refactoring, testing, and other dev tasks.
Code Acceptance
9leyuan0602-glitch/cc-claude-codex
Independent code acceptance skill. Use when verifying completed work before committing, merging, or claiming done. Performs test-based verification only: unit tests, E2E tests, and integration tests. Only cares whether outcomes match expectations, not code implementation. Works standalone or as cc-claude-codex Phase 3.
Adversarial Verification
9kadaliao/claude-code-skills-collection
对抗性验证技能 — 验证代码变更/部署/任务交付物的正确性。不是确认"它能工作",而是尝试"把它搞坏"。用于:(1) 完成非平凡任务后自验 (2) 审查 PR/MR (3) 部署后验证 (4) bobooo 说"验证一下"。灵感源自 Claude Code Verification Agent 设计。
Case Cortex
9accilium/accilium-skills
Build and maintain a Case Cortex — a structured, living, machine-readable representation of a single bounded knowledge-work problem (a "case") that agents and humans share as their reasoning substrate. Use whenever the user wants to set up, seed, update, query, or regenerate artifacts from a Case Cortex. Triggers on phrases like "build a cortex for X", "start a new case", "initialize a case", "seed my cortex", "update the cortex", "add to the cortex", "ingest this document into the cortex", "what does the cortex say about Y", "regenerate the briefing", or "lint the cortex". A Cortex fits bound
Compound Dev
9brijoobopanna/ClaudeSkills
Make Claude Code sessions compound — every session builds on the last instead of starting from scratch. Implements Karpathy's LLM Wiki pattern for software engineering. Use this skill when starting a new project, onboarding to an existing codebase, or any time the user says "set up my project", "add project memory", "create CLAUDE.md", "help me structure this project", "I keep re-explaining things to Claude", "my sessions don't remember anything", "ingest this document", or "run a health check". Also trigger when the user asks about session efficiency, token usage, or wants to improve their Cl
AI Policy Assessment Skill
9accilium/accilium-skills
Checks an existing AI policy and answers the two questions a management team asks: what does the law require of us that we have not covered, and where are we stricter than the law asks, at our own cost. Output is one self-contained HTML report for a business reader: coverage figures, a risk-versus-strictness grid, and 27 criteria with the policy sentence each finding rests on. The client picks the depth up front (quick, standard, extensive); the run then produces the report without an approval step. No network, no plugins; also runs as plain attachments in a chat assistant. Use it for "check o
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.