judgment-day
Skill26 starsChanged 9 days agoMITView on GitHub
Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- JuankCadavid/akili-specstheir own version, first seen Nov 2, 2026
- svg153/skillsedited, first seen Nov 1, 2026
- AndyTechnologies/my-own-skillstheir own version, first seen Oct 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- svg153/skills★ 196% same
Wrote their own version · 2
- JuankCadavid/akili-specs★ 12same name
- AndyTechnologies/my-own-skills★ 0same name
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 repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- acliSkill
- agentic-qa-coreSkill
- agentic-qa-onboardSkill
- bug-screenshot-annotationSkill
- business-api-contextSkill
- business-data-contextSkill
- business-domain-contextSkill
- business-e2e-contextSkill
- evidence-artifactSkill
- exploratory-testingSkill
- framework-developmentSkill
- git-flow-masterSkill
- infra-contextSkill
- iql-contextSkill
- jira-administrationSkill
- orca-orchestrationSkill
- project-contextSkill
- project-discoverySkill
- pr-review-leadSkill
- regression-testingSkill
- session-handoffSkill
- shift-left-testingSkill
- sprint-conductorSkill
- sprint-testingSkill
- test-automationSkill
- test-documentationSkill
- test-framework-adaptationSkill
- xray-cliSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
12
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 38
Wait for both judges before synthesis.
- Distinctive: line 40
Ask before fixing Round 1 confirmed issues.
- Very specific: line 41
After any fix agent runs, immediately re-launch both judges in parallel before commit/push/done/session summary.
- Distinctive: line 43
After 2 fix iterations with remaining issues, ask the user whether to continue.
- Distinctive: line 60
Start Judge A and Judge B concurrently via delegation.
- Distinctive: line 62
Ask before Round 1 fixes; delegate a separate fix agent for confirmed approved fixes only.
- Distinctive: line 64
Before any terminal action, verify every active Judgment Day has a terminal state.
- Distinctive: line 72
J1.: NEVER let the two judges see each other's verdicts before synthesis — blind review is the entire value proposition.
- Distinctive: line 73
J2.: NEVER skip the re-judge step after fixes — fixes can regress other behavior.
- Distinctive: line 74
J3.: NEVER run judgment-day on a diff with > 30 files in a single pass — signal degrades past that size.
- Distinctive: line 75
J4.: NEVER override a judge's reject without documenting WHY in the synthesis — silent overrides destroy the audit trail and the next …
- Distinctive: line 76
J5.: NEVER use judgment-day for trivial typo / format-only / autogenerated diffs — orchestration overhead (two judge agents + synthesis + …
- Distinctive: line 77
J6.: NEVER feed judges different prompts, different criteria, or different context — the blindness only works if both judges see the …
“Common” is measured: kept by at least 6 in 10 of the 3 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
Activation Contract
Load this skill only when the user explicitly asks for Judgment Day, dual/adversarial review, or equivalent Spanish trigger (juzgar, que lo juzguen). Review a specific target: files, feature, PR, or architecture slice.
Within this QA boilerplate, this skill is cited by:
/test-automation— Review phase, as one of the two ways to satisfy its MANDATORY separate verifier (this skill OR/pr-review-lead), for every change, not only high-risk ones. That Review step counts as the explicit request above./git-flow-master— OPTIONAL pre-PR gate when the diff is large or touches shared fixtures / base classes
Outside the /test-automation verifier slot it is never invoked automatically; users opt in via explicit trigger.
Inputs — read these first, in this order
Canonical reading order for any AI starting cold on a Judgment Day review. Read in order; stop earlier when the target is small enough that later inputs add no signal.
- The diff / files / PR / architecture slice under review — the literal target the user named.
AGENTS.md— repo conventions, Critical Rules, behavioral layer (the judges must score against these, not generic best-practice)..agents/skills/REGISTRY.md— skill registry; resolve which project skills apply to the target's file paths + task type, and inject the sameSkills to load before workblock into both judge prompts.- The change's spec / PR description / Jira ticket — the stated intent. Judges score against intent, not their imagined intent.
references/prompts-and-formats.md— judge prompts, fix prompts, warning rubric, verdict table format.- Prior judge outputs from earlier rounds (Round 2+ only) — to detect regressions or stale findings vs. new ones.
Hard Rules
- Resolve project skills before launching agents: read skill registry, match skill paths by target files/task, and inject the same
Skills to load before workblock into both judge prompts and fix prompts. - Launch two blind judges in parallel with identical target and criteria; never review the code yourself.
- Wait for both judges before synthesis; never accept a partial verdict.
- Classify warnings as
WARNING (real)only if normal intended use can trigger them; otherwise downgrade to INFO asWARNING (theoretical). - Ask before fixing Round 1 confirmed issues.
- After any fix agent runs, immediately re-launch both judges in parallel before commit/push/done/session summary.
- Terminal states are only
JUDGMENT: APPROVEDorJUDGMENT: ESCALATED. - After 2 fix iterations with remaining issues, ask the user whether to continue.
Decision Gates
| Condition | Action |
| Target unclear | Ask for scope; do not launch judges. |
| No skill registry | Warn, proceed with generic criteria, and record Skill Resolution: none. |
| Both judges find same CRITICAL/real WARNING | Confirmed; ask/fix according to round rules. |
| One judge finds issue | Suspect; report and triage, do not auto-fix. |
| Judges contradict | Escalate for manual decision. |
| Round 2+ has only theoretical warnings/suggestions | Report as INFO; do not re-judge. |
Execution Steps
- Confirm target and optional custom criteria.
- Resolve exact skill paths from registry or warn if missing.
- Start Judge A and Judge B concurrently via delegation.
- Synthesize findings into confirmed, suspect, contradiction, and INFO buckets.
- Ask before Round 1 fixes; delegate a separate fix agent for confirmed approved fixes only.
- Re-judge in parallel after fixes; repeat until approved, escalated, or user asks to stop.
- Before any terminal action, verify every active Judgment Day has a terminal state.
Output Contract
Return ## Judgment Day — {target} with round number, verdict table, confirmed/suspect/contradiction counts, fixes applied, re-judgment result, Skill Resolution, and final JUDGMENT: APPROVED ✅ or JUDGMENT: ESCALATED ⚠️.
Anti-patterns — NEVER do these
- J1. NEVER let the two judges see each other's verdicts before synthesis — blind review is the entire value proposition; cross-contamination collapses two judges into one.
- J2. NEVER skip the re-judge step after fixes — fixes can regress other behavior; only a fresh dual verdict confirms the change actually landed clean.
- J3. NEVER run judgment-day on a diff with > 30 files in a single pass — signal degrades past that size. Split into focused per-area reviews and synthesize manually.
- J4. NEVER override a judge's reject without documenting WHY in the synthesis — silent overrides destroy the audit trail and the next reviewer cannot tell if the issue was triaged or missed.
- J5. NEVER use judgment-day for trivial typo / format-only / autogenerated diffs — orchestration overhead (two judge agents + synthesis + re-judge loop) exceeds the value of the verdict.
- J6. NEVER feed judges different prompts, different criteria, or different context — the blindness only works if both judges see the identical brief. Asymmetric briefs produce asymmetric verdicts that look like real disagreement but are artifacts.
References
- references/prompts-and-formats.md — judge/fix prompts, warning rubric, verdict tables, and language snippets.
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.

