claude-review
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Use when the user asks Codex to orchestrate Claude for a coding job in another terminal, or to review code, run adversarial or ship/no-ship review, audit security risks, or inspect a large diff/folder.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- KenmegeTheEducatingGP/codex-claude-companionword for word, first seen Nov 16, 2026
- ryanportfolio/Harness-Firmwaretheir own version, first seen Nov 15, 2026
- KroxiDev/engineering-skillstheir own version, first seen Nov 15, 2026
- ryanportfolio/HarnessFirmware.comtheir own version, first seen Nov 12, 2026
- ryanportfolio/Corewise.Academytheir own version, first seen Nov 12, 2026
- AhsanT4riq/claude-plugin-codextheir own version, first seen Nov 8, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions21 projects use a version of this.
Word for word · 1
- KenmegeTheEducatingGP/codex-claude-companion★ 2100% same
Edited · 0
None found.
Wrote their own version · 20
- xiaolai/cc-suite★ 56same name
- smithjohn78390/smith--skills★ 41same name
- yangliu2060/smith--skills★ 40same name
- ulpi-io/browse★ 15same name
- mryll/skills★ 8same name
- plannotator/dev-skills★ 7same name
- KroxiDev/engineering-skills★ 4same name
- sandover/agent-skills★ 4same name
- abdurshd/skills★ 2same name
- ryanportfolio/winuse-mcp★ 2same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the local helper to route the requested Claude lane.
- Distinctive: line 35
Keep review workflows read-only.
- Very specific: line 39
Treat trusted-autonomous as explicit cooperative same-UID host trust, not a sandbox.
- Distinctive: line 44
If the helper exits non-zero, report the exact failure and stop.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Review
Use the local helper to route the requested Claude lane. New coding work uses a durable tmux-owned bridge worker with recorded collaboration, recovery, delivery, and independent verification. The older workspace lane remains available for compatibility. Review lanes snapshot the target, use read-only agentic mode, validate structured output, and render the result.
Default command
codex-claude review -- "$ARGUMENTS"Route by intent
- Coding or implementation:
codex-claude delegate --verify-command '<JSON argv>' -- "$ARGUMENTS"; keep the active Codex task responsive and supervise the returnedccb_...job withwait,status,logs,send, andrecover. - Legacy interactive workspace:
codex-claude workspace -- "$ARGUMENTS"; useworkspace-status,workspace-logs, andworkspace-stop. - Everyday diff review:
codex-claude review -- "$ARGUMENTS" - Release gate / ship-no-ship:
codex-claude review --preset ship -- "$ARGUMENTS" - Security review:
codex-claude review --preset security -- "$ARGUMENTS" - Research or evidence-heavy folder:
codex-claude folder <path> --preset research --long-context -- "$ARGUMENTS" - Deep multi-agent review:
codex-claude review --preset deep --background -- "$ARGUMENTS"
Operating rules
- Keep review workflows read-only. Use a writable bridge or workspace lane only when the user asks for coding or implementation.
- Require an origin-supplied repository-native verification command for every delegation. Do not accept a worker-chosen command as independent verification.
- Treat
trusted-autonomousas explicit cooperative same-UID host trust, not a sandbox. Never claimsandbox-autonomousis available. - The bridge may launch ephemeral Codex for independent verification. Do not hardcode a GPT model or claim the worker verified itself independently.
- Return the helper output verbatim.
- If the helper exits non-zero, report the exact failure and stop.
- For first-run problems, ask the user to run
codex-claude enableandcodex-claude doctor.
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.

