judgment-day

Runs blind dual-agent adversarial code reviews and re-judges fixes until approval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-pass AI code reviews are unreliable: one reviewer misses issues, hallucinates problems, or rubber-stamps its own work. This Skill enforces an adversarial review process where two independent judges review the same target blindly, only agreed-upon findings get fixed, and every fix is re-judged before completion. ## Core Features & Use Cases - Blind Dual Review: Launches two parallel judge agents with identical targets and criteria, then synthesizes findings into confirmed, suspect, contradiction, and INFO buckets. - Fix-and-Rejudge Loop: Delegates confirmed issues to a surgical fix agent, then immediately re-runs both judges before any commit, push, or session summary. - Severity Discipline: Classifies warnings as real only when normal intended use can trigger them, downgrading theoretical issues to INFO to reduce noise. - Use Case: Before merging a PR, ask for a judgment day review of the changed files; the Skill runs both judges, fixes only confirmed CRITICAL and real WARNING findings after your approval, and re-judges until it reaches JUDGMENT: APPROVED or escalates to you. ## Quick Start Ask the AI to run judgment day on the files changed in your current branch and fix any confirmed issues.

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 code review with AI agents?▼

Trigger the judgment day workflow on a specific target such as files, a feature, or a PR. Two blind judge agents review it in parallel with identical criteria, and only findings both judges confirm are treated as real issues.

How does dual review reduce false positives in code review?▼

Findings reported by only one judge are classified as suspect and are never auto-fixed. Warnings are marked real only if normal intended use can trigger them; contrived or impossible paths are downgraded to INFO.

What happens after the judges find confirmed issues?▼

The Skill asks for your approval before Round 1 fixes, then delegates a surgical fix agent that changes only confirmed issues. Both judges immediately re-review the result before any commit, push, or session summary.

When does the judgment day review loop stop?▼

The loop ends only at JUDGMENT: APPROVED or JUDGMENT: ESCALATED. After two fix iterations with remaining issues, it asks whether to continue, and contradictions between judges are escalated for manual decision.

Can I use this review workflow without named sub-agents?▼

Yes. When named JD agents are unavailable, the Skill uses the adapter's generic delegate syntax without an agent parameter, and the model is controlled through the adapter's native model-switching mechanism.