judgment-day

Run blind parallel adversarial code reviews with severity triage and re-review.

9|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/susomejias/rembric --skill judgment-day-susomejias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: judgment-day
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/judgment-day
Command: npx skills add https://github.com/susomejias/rembric --skill judgment-day-susomejias

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual code reviews often miss critical issues due to reviewer bias, fatigue, or oversights, leading to bugs and security vulnerabilities making it into production.

Core Features & Use Cases

  • Blind Parallel Adversarial Review: Launches two independent code reviewers with identical criteria to catch issues a single reviewer would miss.
  • Severity-Based Issue Triage: Classifies findings as critical, real warnings, theoretical warnings, or suggestions to prioritize fixes.
  • Controlled Fix Workflow: Applies only confirmed fixes, then re-runs both reviewers to validate changes before approval.
  • Use Case: Ideal for reviewing high-stakes pull requests, new feature implementations, or architecture changes where you need maximum confidence in code quality.

Quick Start

Use the judgment-day skill to run a dual adversarial review of the open pull request for the user authentication feature.

Frequently Asked Questions about judgment-day

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

FAQPage Schema
What is blind dual code review and how does it catch critical issues?

Blind dual code review runs two independent adversarial reviewers in parallel with identical criteria to catch missed issues. This eliminates reviewer bias and fatigue by classifying findings by severity, ensuring only confirmed fixes get applied.

How do I run an adversarial pull request audit to ensure high-confidence issue detection?

Run an adversarial pull request audit by launching parallel blind reviewers to evaluate the code. The process enforces a controlled workflow where only confirmed fixes are applied, followed by a mandatory post-fix re-review to validate changes.

Does this dual review approach work for architecture slice assessments and new feature implementations?

Yes, this dual review approach works for architecture slice assessments and new feature implementations. It applies to any codebase evaluation requiring high-confidence issue detection, including high-stakes pull requests and feature audits.

What is the best way to triage code review findings by severity?

The best way to triage code review findings by severity is to classify them as critical issues, real warnings, theoretical warnings, or suggestions. This severity-based issue triage prioritizes fixes and ensures only confirmed fixes are applied.

How does the controlled fix workflow prevent unvetted code changes during a code review?

The controlled fix workflow prevents unvetted code changes by applying only confirmed fixes and then re-running both reviewers. This mandatory post-fix re-review validates changes before approval, ensuring no unvetted code makes it into production.

Why does manual code review miss critical security vulnerabilities and bugs?

Manual code review misses critical security vulnerabilities and bugs due to reviewer bias, fatigue, or oversights. Running parallel adversarial code reviews eliminates these missed issues by enforcing strict blind judging protocols.