judgment-day
Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- judgment-day
- license
- Apache-2.0
- metadata
- { "author": "gentleman-programming", "version": "1.4" }
- description
- Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.
02 资源文件 1
- 参考文档references/prompts-and-formats.md2.6 KB
03 SKILL.md 正文
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 compact rules by target files/task, and inject the same
Project Standardsblock 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 asWARNING (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: APPROVEDorJUDGMENT: ESCALATED. - After 2 fix iterations with remaining issues, ask the user whether to continue.
Decision Gates
| Condition | Action |
|---|---|
| Target unclear | Ask for scope; do not launch judges. |
| No skill registry | Warn, proceed with generic criteria, and record Skill Resolution: none. |
| Both judges find same CRITICAL/real WARNING | Confirmed; ask/fix according to round rules. |
| One judge finds issue | Suspect; report and triage, do not auto-fix. |
| Judges contradict | Escalate for manual decision. |
| Round 2+ has only theoretical warnings/suggestions | Report as INFO; do not re-judge. |
Execution Steps
- Confirm target and optional custom criteria.
- Resolve compact project standards from registry or warn if missing.
- Start Judge A and Judge B concurrently via delegation.
- Synthesize findings into confirmed, suspect, contradiction, and INFO buckets.
- Ask before Round 1 fixes; delegate a separate fix agent for confirmed approved fixes only.
- Re-judge in parallel after fixes; repeat until approved, escalated, or user asks to stop.
- 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
- references/prompts-and-formats.md — judge/fix prompts, warning rubric, verdict tables, and language snippets.
04 同仓库更多 Skills
zustand-5
Zustand 5 state management patterns. Trigger: When managing React state with Zustand.
zod-4
Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.