j0k3r-dev-rgl/open-code-config-public/judgment-day

Claude Code and agent skill by j0k3r-dev-rgl/open-code-config-public

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.

Install

npx vskill@latest install j0k3r-dev-rgl/open-code-config-public/judgment-day

SKILL.md

The same SKILL.md was published earlier as santiagoposadag/aprendiz-kit/judgment-day.

Activation Contract

Load this skill only when the user explicitly asks for Judgment Day, dual/adversarial review, or equivalent Spanish trigger (juzgar, que lo juzguen). Review a specific target: files, feature, PR, or architecture slice.

Hard Rules

  • Resolve project skills before launching agents: read skill registry, match skill paths by target files/task, and inject the same Skills to load before work block into both judge prompts and fix prompts.
  • Launch two blind judges in parallel with identical target and criteria; never review the code yourself.
  • Wait for both judges before synthesis; never accept a partial verdict.
  • Classify warnings as WARNING (real) only if normal intended use can trigger them; otherwise downgrade to INFO as WARNING (theoretical).
  • Ask before fixing Round 1 confirmed issues.
  • After any fix agent runs, immediately re-launch both judges in parallel before commit/push/done/session summary.
  • Terminal states are only JUDGMENT: APPROVED or JUDGMENT: ESCALATED.
  • After 2 fix iterations with remaining issues, ask the user whether to continue.

Decision Gates

ConditionAction
Target unclearAsk for scope; do not launch judges.
No skill registryWarn, proceed with generic criteria, and record Skill Resolution: none.
Both judges find same CRITICAL/real WARNINGConfirmed; ask/fix according to round rules.
One judge finds issueSuspect; report and triage, do not auto-fix.
Judges contradictEscalate for manual decision.
Round 2+ has only theoretical warnings/suggestionsReport as INFO; do not re-judge.

Execution Steps

  1. Confirm target and optional custom criteria.
  2. Resolve exact skill paths from registry or warn if missing.
  3. Start Judge A and Judge B concurrently via delegation.
  4. Synthesize findings into confirmed, suspect, contradiction, and INFO buckets.
  5. Ask before Round 1 fixes; delegate a separate fix agent for confirmed approved fixes only.
  6. Re-judge in parallel after fixes; repeat until approved, escalated, or user asks to stop.
  7. Before any terminal action, verify every active Judgment Day has a terminal state.

Output Contract

Return ## Judgment Day — {target} with round number, verdict table, confirmed/suspect/contradiction counts, fixes applied, re-judgment result, Skill Resolution, and final JUDGMENT: APPROVED ✅ or JUDGMENT: ESCALATED ⚠️.

References

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/j0k3r-dev-rgl/open-code-config-public/judgment-day/badge)](https://verified-skill.com/skills/j0k3r-dev-rgl/open-code-config-public/judgment-day)

Something wrong with this skill or its page? Tell us.