judgment-day

Runs parallel blind dual-judge adversarial code reviews with fix and re-judgment cycles.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jhannka/php-skills --skill judgment-day-jhannka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: judgment-day
Source: https://github.com/jhannka/php-skills/tree/main/skills/judgment-day
Command: npx skills add https://github.com/jhannka/php-skills --skill judgment-day-jhannka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-reviewer code reviews miss edge cases and suffer from individual blind spots, letting bugs slip into production. This protocol launches two independent blind judge sub-agents in parallel against the same target, synthesizes their findings, applies fixes, and re-judges until both pass or the user escalates. ## Core Features & Use Cases - Parallel Blind Review: Two judge sub-agents review the same target independently via async delegation, with no cross-contamination, then the orchestrator synthesizes confirmed, suspect, and contradictory findings into a verdict table. - Warning Classification & Convergence: Findings are split into CRITICAL, real WARNING, theoretical WARNING, and SUGGESTION, with a convergence threshold that stops diminishing-returns re-judge cycles after Round 1. - Fix and Re-judge Loop: A separate Fix Agent applies only confirmed issues, then fresh judges re-review; after 2 iterations the user decides whether to continue or escalate. - Use Case: Before merging a significant feature, ask for a judgment day review so two adversarial reviewers independently hunt for correctness, security, performance, and convention issues, then confirmed bugs are fixed and re-verified automatically. ## Quick Start Ask the agent to run judgment day on the specific files or feature you want reviewed before merging.

Frequently Asked Questions about judgment-day

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial dual code review with AI agents?

Trigger the protocol by asking for a judgment day review on a specific target. Two blind judge sub-agents are launched in parallel with identical criteria, their findings are synthesized into a verdict table, and confirmed issues are fixed and re-judged.

What is blind parallel code review and why use two reviewers?

Blind parallel review means two agents review the same code independently without knowing about each other. Findings confirmed by both are high-confidence, while single-judge findings are flagged as suspects, reducing individual reviewer blind spots.

How does the protocol decide when a review is approved?

A target is approved when both judges return clean, or after Round 2 when zero confirmed CRITICALs and zero confirmed real WARNINGs remain. Theoretical warnings and suggestions may remain without blocking approval.

What happens if issues remain after multiple fix iterations?

After two fix iterations with remaining issues, the protocol asks the user whether to continue iterating. If the user declines, the review is marked ESCALATED with a report of remaining issues for manual human review.

When should I not use a dual-judge adversarial review?

Avoid it for trivial changes where two review rounds cost more than the risk of a bug, or when the target scope is unclear. The protocol requires a specific, well-defined target before launching judges.