judgment-day

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

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

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 one immutable target with identical scope and criteria, then merges their findings into a frozen ledger. - Bounded fix rounds: Applies fixes only to 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, verdict YAML, and a terminal state of either approved or escalated, with contradictions escalated for human decision. - Use Case: Before merging a critical pull request, request a Judgment Day review so two independent judges verify correctness, security, and error handling, and only mutually confirmed severe defects are corrected. ## Quick Start Ask the AI to run Judgment Day dual review on the specific files or changes you want verified.

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 or an equivalent dual review for a concrete target. The orchestrator builds one immutable target, launches two blind read-only judges in parallel with identical scope, and merges their findings into a frozen ledger.

What happens when the two review judges disagree?▼

When judges contradict each other, the finding is escalated for an explicit human decision rather than auto-fixed. Findings reported by only one judge are recorded as suspects and are never corrected automatically.

How many fix rounds does the review process allow?▼

The process permits at most two fix rounds and two scoped re-judgments. If any severe issue remains after the second re-judgment, the transaction is escalated and stopped; no third round exists.

Which findings get fixed automatically in dual review?▼

Only severe findings confirmed by both judges are eligible for correction, and the parent orchestrator asks before the first fix round. Warnings and suggestions remain informational and are never auto-fixed.

What are the limitations of the judgment-day review workflow?▼

It requires an explicit user trigger and a clearly scoped target, and it never runs alongside an ordinary review for the same target. Terminal states are only approved or escalated, and exhausted lineages cannot be reset or extended.