judgment-day

Runs blind dual-judge adversarial code review with bounded fix and re-judgment rounds.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill judgment-day-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: judgment-day
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/judgment-day
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill judgment-day-ad-paladins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-reviewer code reviews can miss defects or produce unverified findings. This Skill orchestrates an explicit dual-review process where two blind, read-only judges independently inspect the same immutable target, so only findings confirmed by both judges trigger fixes. ## Core Features & Use Cases - Blind Dual Review: Launches two independent judges in parallel against an identical immutable target with identical criteria, then merges their findings into a frozen ledger. - Bounded Fix Rounds: Applies fixes only for severe findings confirmed by both judges, with at most two fix rounds and two scoped re-judgments before escalation. - Structured Verdicts: Produces a frozen ledger with confirmed, suspect, contradiction, and info counts, ending in exactly one terminal verdict: APPROVED or ESCALATED. - Use Case: Before merging a critical pull request, request a Judgment Day review so two independent judges verify correctness, security, and edge cases, and any confirmed severe defect is fixed and re-judged within a bounded loop. ## Quick Start Ask the assistant to run Judgment Day on a specific target, for example: run judgment day dual review on the changes in src/payments.

Frequently Asked Questions about judgment-day

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

FAQPage Schema
How do I run a dual adversarial code review?▼

Explicitly request Judgment Day for a concrete target, such as a pull request or directory. The orchestrator launches two blind read-only judges in parallel against the same immutable target, merges their findings, and only fixes severe issues both judges confirm.

What is blind dual review in code review workflows?▼

Blind dual review means two independent judges inspect the same target with identical scope and criteria without seeing each other's work. Agreement between the two judges serves as the corroboration mechanism, replacing a separate refuter pass.

When should I use Judgment Day instead of a standard review?▼

Use it when you explicitly want adversarial dual review for a concrete target, since it replaces the ordinary review flow for that target. It is suited to high-risk changes where confirmed findings and bounded fix rounds matter more than speed.

What happens when the two judges disagree on a finding?▼

A finding reported by only one judge is recorded as a suspect and is never auto-fixed. If the judges directly contradict each other, the review escalates for an explicit human decision instead of proceeding.

How many fix rounds does the review allow before escalating?▼

The process permits at most two fix rounds and two scoped re-judgments. If any severe issue remains after the second re-judgment, the review terminates with an escalated verdict and no third round exists.