skills.rest
zMynxx
zMynxxCOMMUNITY
Explore all skills by this author →
GitHub

judgment-day

Coordinate parallel adversarial code reviews with structured issue triage and verification cycles.

Updated Jun 5, 2026
Search Tags:#code review#pull request#software quality#bug detection#review workflow#judgment#adversarial review
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?

This Skill prevents incomplete or biased reviews by coordinating independent adversarial judgments, structured issue triage, and verification cycles before changes are accepted.

Core Features & Use Cases

  • Blind Dual Review: Launches two independent judges with identical criteria to identify confirmed, suspect, and contradictory findings.
  • Controlled Fix Workflow: Applies only confirmed issues after approval and automatically triggers re-review cycles after fixes.
  • Use Case: Review a feature, pull request, or architecture change with parallel reviewers to validate correctness, edge cases, security concerns, and implementation quality before completion.

Quick Start

Use the judgment-day skill to perform an adversarial review of the specified feature and report the final judgment result.

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 on a pull request?▼

To run an adversarial code review on a pull request, launch the dual review workflow to execute independent judges that identify confirmed, suspect, and contradictory findings before synthesizing a final verdict.

What is dual adversarial code review and how does it validate software quality?▼

Dual adversarial code review is a process that coordinates two independent judges with identical criteria to validate software quality by cross-referencing findings into confirmed, suspect, or contradictory categories.

Can I use this adversarial review workflow for architecture slices and individual files?▼

Yes, the adversarial review workflow applies to architecture slices, individual files, and features, providing structured issue triage and verification cycles for any targeted code changes.

How does the controlled fix workflow handle confirmed issues after a code review?▼

The controlled fix workflow applies only confirmed issues after approval and automatically triggers re-review cycles to verify fixes, ensuring validated software quality before changes are accepted.

What is the best way to prevent biased code reviews during pull requests?▼

The best way to prevent biased code reviews is to use parallel reviewer execution with independent judgment workflows, synthesizing verdicts only after controlled re-judgment cycles validate the findings.

Related Skills

Explore More Software Engineering Skills→
DethonDethon
3

requesting-code-review

Generate reviewer-ready summaries of code changes with task details and changed files.

Community
Basic
richkuorichkuo
45

fix-pr-review-loop

Automate pull request review feedback resolution via GitHub CLI.

Community
Advanced
bryonjacobbryonjacob

configuring-java-stack

Configure a Java stack with Maven, JUnit 5, Spotless, SpotBugs, and JaCoCo.

Community
Advanced
thiagoooo34252thiagoooo34252
1

judgment-day

Launch parallel adversarial code reviews with two independent sub-agents.

Community
Advanced