judgment-day

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-reviewer code reviews can miss defects or produce unchallenged false positives. This Skill orchestrates an explicit adversarial review where two blind, read-only judges independently inspect the same immutable target, and only findings confirmed by both trigger bounded fixes. ## Core Features & Use Cases - Blind Dual Review: Launches two independent judges (jd-judge-a, jd-judge-b) in parallel against one frozen 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 that inspect only the ledger plus fix delta. - Deterministic Verdicts: Returns exactly one terminal verdict, JUDGMENT: APPROVED or JUDGMENT: ESCALATED, with confirmed/suspect/contradiction counts and artifact references. - Use Case: Before merging a critical authentication module, request a Judgment Day review so two independent judges verify correctness, security, and error handling, with contradictions escalated for human decision. ## Quick Start Ask the assistant to run Judgment Day dual review on the specific files or module you want adversarially reviewed.

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. The orchestrator freezes the target, launches two blind read-only judges in parallel with identical scope, merges their findings, and runs at most two bounded fix and re-judgment rounds.

How does dual-judge review handle disagreements between reviewers?

Findings confirmed by both judges become confirmed severe items eligible for fixing. Findings reported by only one judge are recorded as suspects without auto-fix, and direct contradictions between judges are escalated for an explicit human decision.

What verdicts can an adversarial code review produce?

The only terminal verdicts are APPROVED and ESCALATED. If severe findings remain after the second scoped re-judgment, the review escalates and stops; the round budget is never reset or extended.

Does this review approve commits, pushes, or releases?

No. A judgment issues no receipt and carries no delivery authority, so it satisfies no commit, push, PR, or release gate. Delivery authority requires running the ordinary negotiated review lifecycle as a separate step.

When should I not use dual blind review?

Avoid it for routine low-risk changes where a single review pass suffices, since it requires building an immutable target and coordinating two judges plus a fix actor. It also never runs alongside the ordinary 4R review method on the same target.