codex-debate
Skill963 starsChanged 5 months agoLicence not identifiedView on GitHub
Run an automated codex⇄Claude debate to consensus — no round cap, no deadlock exit. Two explicit subcommands. `review` (also the bare/back-compat default) — codex (reviewer) critiques the current diff and a Claude subagent (author) fixes/disputes, looping until they agree. `answer` — Claude and codex each answer a freeform prompt in parallel, then cross-check until they agree, and a unified answer is returned. Use when the user types `/codex-debate`, asks to "have codex review this", "run the codex debate", "review this PR with codex", "argue this with codex until you agree", or passes a question to "have Claude and codex debate/answer until they agree".
In this repository54 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- be-reviewSkill
- beSkill
- ciSkill
- code-policeSkill
- codex-debateSkill
- doSkill
- dpella-mcpSkill
- eleganceSkill
- fact-checkSkill
- forge-prSkill
- frontend-designSkill
- hickeySkill
- koluSkill
- lens-debateSkill
- lowySkill
- nix-chrome-devtools-mcpSkill
- nix-for-devSkill
- nix-haskellSkill
- nix-justfileSkill
- nix-playwrightSkill
- odu-mcpSkill
- perfection-reviewSkill
- puSkill
- ralphSkill
- surfaceSkill
- talkSkill
- be-reviewSkill
- beSkill
- ciSkill
- code-policeSkill
- doSkill
- dpella-mcpSkill
- eleganceSkill
- fact-checkSkill
- forge-prSkill
- frontend-designSkill
- hickeySkill
- koluSkill
- lens-debateSkill
- lowySkill
- nix-chrome-devtools-mcpSkill
- nix-for-devSkill
- nix-haskellSkill
- nix-justfileSkill
- nix-playwrightSkill
- odu-mcpSkill
- perfection-reviewSkill
- puSkill
- ralphSkill
- surfaceSkill
- talkSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 1 is distinctive, and 13 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.