review-gate
Skill24 starsChanged 2 days agoMITView on GitHub
Review a change before it is committed or pushed with three independent reviews that block only when all three request changes. Use when asked to review before committing or pushing, gate a push, check "is this safe to push", explain or skip a block from the pre-commit hook's model review, or run a pre-push review. Runs three reviews through review3.py (the Codex CLI, or the Claude CLI on Haiku when Codex is missing), and three Haiku subagent reviews (or one advisory review) when neither CLI is available.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
- s977043/PlanGatetheir own version, first seen Nov 12, 2026
- jame-hv/brse-toolkittheir own version, first seen Nov 8, 2026
- XuHo-IT/Content-Agent-Kittheir own version, first seen Nov 8, 2026
- weedmo/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use workflow-router, afk and 6 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.
parcadeiSkillworkflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
Also in 3 projects that use this
jaaxkSkillafk
Toggle AFK (Away From Keyboard) mode. When enabled, a PostToolUse hook sends a summary of every tool (that involves writing to files or changing settings) Claude runs to a dedicated Slack thread so the user can monitor remotely. Toggle on with /afk, toggle off with /afk again.
Also in 3 projects that use this
AnthropicSkillperformance-review
Structure a performance review with self-assessment, manager template, and calibration prep. Use when review season kicks off and you need a self-assessment template, writing a manager review for a direct report, prepping rating distributions and promotion cases for calibration, or turning vague feedback into specific behavioral examples.
Also in 3 projects that use this
yakatotechSkilladvisor
Provide improvement suggestions and advice on work content. Use for document review, efficiency suggestions, and best practices
Also in 3 projects that use this
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 4 projects that use this
MicrosoftSkilldiagnose
Use to systematically diagnose why scenarios fail — identifies root causes by analyzing agent traces, codebase, and behavioral patterns
Also in 3 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- KerberosClaw/kc_ai_skills★ 79same name
- vanillagreencom/kendex★ 76same name
- usk6666/yorishiro-proxy★ 19same name
- XuHo-IT/Content-Agent-Kit★ 8same name
- finolabs/finolabs-vibecode★ 4same name
- finolabs/vibecode★ 4same name
- s977043/PlanGate★ 3same name
- toverux/cantrips★ 3same name
- 0xUrsanomics/utopia-os★ 2same name
- 17-sss/agent-skills★ 2same name
11 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- framework/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversarial-testsSkill
- app-introspectSkill
- chaos-testSkill
- component-buildSkill
- eval-reportSkill
- gofastr-docsSkill
- gofastr-hostSkill
- gofastr-mcp-debugSkill
- gofastr-uiSkill
- log-debugSkill
- plain-wordsSkill
- primitives-sweepSkill
- twin-sweepSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 8 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run python3 .claude/skills/review-gate/review3.py --check (on Windows, python).
- Distinctive: line 26
Exit 0: script mode: Use it.
- Very specific: line 33
Run review3.py from the repository.
- Distinctive: line 63
No Codex does not block: the same three runs go to the Claude CLI on Haiku.
- Very specific: line 80
When it blocks: fix the findings and commit again.
- Distinctive: line 94
Start three reviewers. Give each one the filled prompt and nothing else: no conversation history, no summary of the change, no hint of what …
- Very specific: line 98
Use the same model for all three.
- Distinctive: line 101
If your environment caps how many agents run at once, run them in batches.
- Distinctive: line 103
Read each answer's JSON object.
- Distinctive: line 126
Add a second pass that verifies or re-judges the findings.
- Distinctive: line 129
Add extra context to the prompt, such as fact packets or code-graph pointers.
- Distinctive: line 131
Run the review as one request with no tools.
- Very specific: line 132
Use codex exec review with only P0 and P1 counted as blocking.
“Common” is measured: kept by at least 6 in 10 of the 18 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
Review gate
Three reviews of the same change, same prompt, same model, each started fresh. Block the push only if all three request changes. Report the blocking findings from every run, not just the ones they agree on.
Pick a mode
Run python3 .claude/skills/review-gate/review3.py --check (on Windows,
python). It prints the reviewer binary it found and exits 0, or exits 3.
For Codex it looks at --codex PATH, then CODEX_BIN, then PATH, then the
usual install spots: on macOS the ChatGPT app's own CLI
(ChatGPT.app/Contents/Resources/codex-cli/bin/codex under
/Applications or ~/Applications), then every nvm node version newest
first ($NVM_DIR/versions/node/*/bin/codex), and on Windows nvm-windows
(%NVM_HOME%\v*\codex.cmd) and npm's global dir
(%APPDATA%\npm\codex.cmd). With no Codex it falls back to the Claude
Code CLI: --claude PATH, then CLAUDE_BIN, then claude on PATH. The
exit-3 message names each place tried.
- Exit 0: script mode. Use it.
- Exit 3, or you cannot run commands or Python: subagent mode.
- You cannot start other agents either: single mode. One review, advisory only.
Script mode
- Run
review3.pyfrom the repository. With no arguments it reviews the unpushed commits,@{upstream}...HEAD, falling back toorigin/HEAD...HEADon a branch with no upstream. Pass--range A...Bfor another range,--stagedfor what the next commit holds (git diff --cached), or--uncommittedforgit diff HEAD. - It starts three reviewer sessions in parallel. With Codex:
codex exec, read-only sandbox, modelgpt-6-luna(--modelorPUSH_REVIEW_MODELto change), high effort, web search off, user config ignored, nothing saved. Without Codex:claude -p, modelhaiku(--modelorPUSH_REVIEW_CLAUDE_MODELto change), limited to reading and searching files (no shell, so no git: a long diff is saved to a file for it), no settings or MCP servers loaded, nothing saved. The result line names the reviewer and model used. - It prints the decision, the vote and every blocking finding with the
runs that raised it.
--jsonprints the same as JSON. - Exit codes: 0 approve, 1 block, 2 fewer than three usable answers or any other failure (a git error, a reviewer that will not start, a crash), 3 no reviewer (neither Codex nor Claude). Only the vote exits 1. On 2, read the run logs it names, then rerun or fall back to subagent mode. Never count a failed run as a vote either way.
In the pre-commit hook
.githooks/pre-commit runs review3.py --staged on every commit, so
an agent that commits gets the review without asking for it:
- It starts after vet and the repo analyzers pass and runs beside the test sweep, so it adds little to the hook's time. Its result prints last.
- 3 of 3 request changes fails the commit and prints the findings.
- No Codex does not block: the same three runs go to the Claude CLI on Haiku.
- With neither CLI the hook warns, names the places it looked, and lets the commit through. Run subagent mode yourself before you push.
- Anything else lets the commit through too: an approve, an incomplete review, or no Python.
- A run that takes longer than ten minutes counts as incomplete
(
GOFASTR_COMMIT_REVIEW_TIMEOUTsets the seconds). If the hook exits early, it stops the review and the commands its runs started. - It skips merge, cherry-pick and revert commits, and commits that stage only Markdown.
- It reviews the index the commit is built from, so
git commit <paths>is reviewed as committed. - The reviewer runs start without git's per-repo variables
(
GIT_INDEX_FILE,GIT_DIRand the rest): a reviewer that runs git or the tests must not write into the commit's index.
When it blocks: fix the findings and commit again. If you read a finding
and it is wrong, commit with GOFASTR_SKIP_COMMIT_REVIEW=1 and say in the
commit message which finding you rejected and why. Never use
--no-verify: it skips every other check too.
Subagent mode
- Work out the range the same way the script does, and fill in
prompt.mdyourself:{repo}is the repository's directory name,{range}the range,{log}the output ofgit log --format='%h %s%n%n%b' <A>..<B>, and{diff}the output ofgit diff <range>inside a diff fence. If the diff is over about 120,000 characters, putgit diff --stat <range>there instead, with a line telling the reviewer to read the full diff with git. - Start three reviewers. Give each one the filled prompt and nothing
else: no conversation history, no summary of the change, no hint of
what you suspect. Each must be able to read the repository and run
git. Tell them not to edit files.
- Use the same model for all three. In Claude Code, use the Agent
tool with
model: haiku. If you can delegate to a Codex model instead, usegpt-6-luna. - If your environment caps how many agents run at once, run them in batches. The three must be independent; they need not be concurrent.
- Use the same model for all three. In Claude Code, use the Agent
tool with
- Read each answer's JSON object. An answer with no JSON object, or a reviewer that failed, is not a vote: start a replacement until you have three answers.
- Vote and report as in script mode, and say the result came from subagent mode.
Single mode
Review the change yourself against the filled prompt.md, in the same
JSON shape. Report it as one vote: list the findings, recommend a look at
any blocking one, and do not call it a block.
Report
- 3 of 3 request changes: block. List every blocking finding with the runs that raised it. A finding only one run raised still belongs in the list.
- 2 of 3 or fewer: approve. List the minority's blocking findings as worth a look, not as blockers.
- Fewer than three usable answers: say so. Do not decide on two.
Do not
- Add a second pass that verifies or re-judges the findings.
- Change the prompt to a skeptic prompt, a checklist, or a different lens per run. All three runs get the same plain prompt.
- Add extra context to the prompt, such as fact packets or code-graph pointers.
- Run the review as one request with no tools.
- Use
codex exec reviewwith only P0 and P1 counted as blocking. If you use it, count P2 as blocking.
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.

