judge
Skill26 starsChanged yesterdayMITView on GitHub
Use when a pull request, branch, or diff must be reviewed before merge or auto-merge, including PRs a subagent built. Triggers on "judge this PR", "review this PR", "review before merge", "revise esse PR", "julga esse PR", "faz o code review", "pode mergear?".
12 other projects use a version of this.
Adopted by
Most recently taken up by
- joi-fairshare/agentic-workflowtheir own version, first seen Nov 14, 2026
- JHostalek/dotclaudetheir own version, first seen Nov 1, 2026
- ilang-ai/autocodetheir own version, first seen Nov 1, 2026
- jthorare/agentic-workflowtheir own version, first seen Oct 25, 2026
- simota/agent-skillstheir own version, first seen Oct 23, 2026
- 2389-research/test-kitchentheir own version, first seen Sep 25, 2026
Used with
Projects with it also use review.
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.
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- nudgebee/nudgebee★ 525same name
- ilang-ai/autocode★ 106same name
- simota/agent-skills★ 99same name
- rvdbreemen/adr-kit★ 13same name
- JHostalek/dotclaude★ 11same name
- 2389-research/test-kitchen★ 4same name
- Walllmat/verdict★ 4same name
- joi-fairshare/agentic-workflow★ 3same name
- jthorare/agentic-workflow★ 3same name
- 2389-research/speed-run★ 1same name
2 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 repository46 other files it gives its agents.
- asaasSkill
- betterauth-integrationSkill
- bullmq-game-queuesSkill
- character-design-narrativeSkill
- ci-cd-gameSkill
- claude-agent-sdkSkill
- database-performance-tuningSkill
- elevenlabs-sound-musicSkill
- foundry-vtt-devSkill
- game-anti-cheatSkill
- game-backend-architectureSkill
- game-blenderSkill
- game-clientSkill
- game-design-fundamentalsSkill
- game-architectSkill
- game-balanceSkill
- game-buildSkill
- game-expandSkill
- game-loreSkill
- game-questSkill
- game-reviewSkill
- game-devSkill
- game-economy-designSkill
- game-godotSkill
- game-localizationSkill
- gameplay-analyticsSkill
- game-save-loadSkill
- game-state-syncSkill
- game-unitySkill
- level-designSkill
- matchmaking-systemSkill
- mmo-designSkill
- monitoring-game-opsSkill
- nuvemshop-sdkSkill
- openclaw-genieSkill
- postgres-game-schemaSkill
- procedural-genSkill
- quest-mission-designSkill
- quest-narrative-coherenceSkill
- react-animationsSkill
- redis-game-patternsSkill
- skill-progression-treesSkill
- story-structure-gameSkill
- stripe-game-paymentsSkill
- ui-ux-gameSkill
- worldbuildingSkill
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 10 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 15
Terminal only: Never post a review, comment, or approval to GitHub.
- Distinctive: line 17
Nothing external from memory: Read the current docs, changelog, or advisory before claiming how a dependency behaves.
- Distinctive: line 46
Run the repo's typecheck, lint, and the tests that cover the changed files.
- Very specific: line 81
Write findings.json in scratch, then run from the repo root:
“Common” is measured: kept by at least 6 in 10 of the 10 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
Judge
Review a change before merge, report in the terminal, then fix what the review found. The report shows what was checked as well as what was found, so the reader can see where the review did not look.
Adapted from The Judge v1.4.0 by Felipe Rodrigues (github.com/felipfr) and Tech Leads Club, https://github.com/tech-leads-club/agent-skills, under CC-BY-4.0 (https://creativecommons.org/licenses/by/4.0/). Modified: terminal report instead of a GitHub review, a coverage table, fresh-context reviewers, and a fix loop. Licence details: NOTICE.md.
Rules
- Terminal only. Never post a review, comment, or approval to GitHub.
- Evidence for every finding. A claim about this repo cites a
path:lineyou read. A claim about a library, API, or framework cites an official URL fetched during this review. A blocker that can be reproduced locally carries the command and its output. - Nothing external from memory. Read the current docs, changelog, or advisory before claiming how a dependency behaves. Inconclusive research turns the finding into a question.
- Report every real issue. Severity and validity are separate: a small real issue is a nit, not a discard. Drop a finding only for lack of evidence.
- Tooling findings are check results. What lint, typecheck, and tests catch goes under "Checks run", not under findings.
- Reviewers did not write the code. Passes run in subagents with fresh context. The main session verifies.
- Coverage is part of the report. A file no pass read is listed as not reviewed. A review reports what it checked; it cannot prove nothing was missed, and the report must not say otherwise.
Severity
| Severity | Meaning | Verdict |
| 🔴 blocker | Data loss, exploitable security, wrong money, broken auth, irreversible migration, PII in logs | FIX_FIRST |
| 🟠 should-fix | Real defect that is not a merge risk | FIX_FIRST |
| 🟡 nit | Minor | none |
| 🟣 pre-existing | Bug this change did not introduce | none; report as follow-up |
Verdict is MERGE only with zero open 🔴 and 🟠. A finding the user accepts in their own words counts as closed: set status to accepted and put the quote in accepted_reason.
Workflow
Step 0: Resolve the change
With a PR: gh pr view <n> --json number,title,body,baseRefName,headRefName and gh pr diff <n>. Without one: diff the branch against its merge base with the default branch. Save the diff and the changed-file list to scratch files.
Classify each changed file as core or skipped (lockfiles, generated code, snapshots, vendored deps, build output). Every skipped file needs a reason. Code deleted in one place and added identically in another is a move; do not review it as new.
Step 1: Deterministic checks
<judge-skill-dir> below is the folder this SKILL.md lives in.
Run the repo's typecheck, lint, and the tests that cover the changed files. Record the exact counts. If a check is not configured, say so. Then run the bypass scan on the diff:
python3 <judge-skill-dir>/scripts/scan_bypasses.py < diff.patchEach hit is a candidate for Pass F, not a finding.
Step 2: Research
List every external surface the diff touches: dependencies added or bumped, APIs called, version-sensitive framework and language features. Read the official source for each and log the URL with the claim it supports or refutes. If the diff touches none, write that.
Step 3: Review passes
Dispatch reviewers as subagents. Under 400 changed core lines: one reviewer runs all passes. Above that: three reviewers in parallel (A+B, C+D, E+F). Run reviewers one model tier below this session when the harness lets you choose a model.
Each dispatch prompt carries: the diff path, the core file list, the Step 1 and Step 2 results, the absolute path of this skill's references/review-standards.md with an instruction to read it first, and the return shape below.
- A. Correctness and logic
- B. Security
- C. Structure and maintainability
- D. AI slop and useless comments
- E. Claims in the PR description or commit messages
- F. Bypasses, duplication, and gambiarras
Each reviewer returns: candidate findings (claim, severity, evidence), and for every core file the passes it actually read that file for. A reviewer that ran out of room says which files it did not reach.
If Claude Code's built-in code-review skill is available, run it on the same target as a second, independent reviewer, with high <target>. Never pass --fix or --comment. Its findings join the candidates for Step 4. It reports no per-file passes, so it adds findings but never counts toward coverage.
Step 4: Verify
In the main session, for each candidate: open the cited location and confirm the claim. Reproduce 🔴 candidates from A and B when a test or short script inside the repo can do it; a feasible reproduction that fails kills the finding. Deduplicate. Set final severity; a blocker you are not sure of becomes a 🟠 question.
Step 5: Gate
Write findings.json in scratch, then run from the repo root:
python3 <judge-skill-dir>/scripts/judge_gate.py findings.json changed-files.txt{
"round": 1,
"verdict": "FIX_FIRST",
"files": {"core": ["src/billing/invoice.ts"], "skipped": [{"path": "bun.lock", "reason": "lockfile"}]},
"coverage": {"src/billing/invoice.ts": ["A", "B", "C", "D", "F"]},
"unverified": [],
"claims": [{"claim": "fixes the rounding bug", "evidence": "tests/invoice.test.ts:40"}],
"findings": [{
"id": "F1", "path": "src/billing/invoice.ts", "line": 142, "severity": "blocker", "status": "open",
"claim": "applyDiscount divides by items.length with no empty-list guard",
"evidence": [{"type": "internal", "ref": "src/billing/invoice.ts:142"}]
}]
}A core file a pass did not reach goes in unverified as {"path": "...", "reason": "..."}. Evidence type is internal (path:line, relative to the repo root), external (an https URL) or repro (the command and its output). A fixed finding needs fixed_in naming the commit.
The gate fails when:
- a changed file is neither core nor skipped, or a skipped file has no reason;
- a core file lacks a pass and has no
unverifiedentry; - a cited
path:linedoes not exist or points outside the repo; - a 🔴 or 🟠 has no evidence;
- finding ids repeat,
claimsis missing, orroundis not 1 to 3; - the verdict disagrees with the open findings. Fix the input until it exits 0. Do not edit the gate.
Step 6: Report
Print these sections in this order:
- Verdict:
MERGEorFIX_FIRST, and the reason in one sentence. - Findings: ID, severity,
path:line, claim, fix. State the problem and its location first, then the smallest fix that works, at the root cause. - Coverage: one row per core file with the passes that read it.
- Not verified: files or passes the review did not reach, and why. Write "none" if empty.
- Hardening notes: see review-standards.md, Pass B.
- Research log: URLs and what each supports or refutes.
- Checks run: Step 1 counts.
- Skipped files with reasons.
- Promote to lint rule: findings a linter could catch next time, or "none".
Step 7: Fix
Fix when the skill runs as the pre-merge gate on work the user already approved. If the user asked a question ("pode mergear?", "what's wrong with this PR?") or asked for a report, stop after Step 6.
Fix every 🔴 and 🟠. Fix 🟡 inside the change's scope. Leave 🟣 as follow-ups.
After fixing, run a new round: rerun Step 1, mark each finding fixed (with fixed_in naming the commit) or open, and send the fix diff to a fresh subagent that looks for new 🔴 only. Add files the fix touched to the file list and coverage. Rerun the gate and print the report again.
Two fix rounds at most. If a 🔴 or 🟠 is still open after the second fix round (round 3), stop and give the user the open findings and what was tried. Do not merge or enable auto-merge while the verdict is FIX_FIRST.
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.

