Agent Skills
› Gentleman-Programming/gentle-ai
› judgment-day
judgment-day
GitHubJudgment Day 技能提供双盲对抗性代码审查机制，通过并行运行两个独立法官评估目标，仅在双方确认严重问题时触发修复，支持最多两轮修正与复审，确保审查的客观性与严谨性。
Trigger Scenarios
用户明确要求执行 Judgment Day 或对抗性审查
需要对特定目标进行高可靠性的双重验证
Install
npx skills add Gentleman-Programming/gentle-ai --skill judgment-day -g -y
SKILL.md
Frontmatter
{
"name": "judgment-day",
"license": "Apache-2.0",
"metadata": {
"author": "gentleman-programming",
"version": "1.7"
},
"description": "Trigger: judgment day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix\/re-judgment rounds."
}
Activation Contract
Load only when the user explicitly requests Judgment Day or equivalent dual/adversarial review for a concrete target. Judgment Day is a standalone developer tool: judges run whenever asked, on any runtime, and need no review transaction, runtime identity, or delivery-receipt machinery to start. It replaces ordinary 4R as the adversarial method for that target; never run both.
Hard Rules
- Resolve matching project skills before starting and pass the same paths to both judges (
jd-judge-a,jd-judge-b) and the fix actor (jd-fix-agent). - Build one complete immutable target, then launch two blind read-only judges in parallel with identical scope and criteria.
- Each judge returns one neutral findings result and terminates. Wait for both; never accept a partial judgment.
- Never launch
review-refuter; two-judge agreement is the corroboration mechanism. - Only the parent orchestrator merges/persists findings, launches the fix actor (
jd-fix-agent), and launches scoped re-judgment. - Fix only severe findings confirmed by both judges. WARNING/SUGGESTION rows remain
info. - Permit at most two fix rounds and two scoped re-judgments. Re-judgment sees only the frozen ledger plus fix delta and may record fix-caused defects.
- The only terminal verdicts are
APPROVED | ESCALATED; never reset or extend an exhausted round budget. - A judgment issues no receipt and carries no delivery authority: it satisfies no commit, push, PR, or release gate. When the caller explicitly wants delivery authority for the same target, run the ordinary negotiated review lifecycle as its own step; a runtime that cannot uphold receipt guarantees loses the receipt, not the judgment.
Decision Gates
| Condition | Action |
|---|---|
| Target unclear | Ask one scope question and stop. |
| Both judges confirm severe finding | Ask before round-one correction; then use the bounded fix actor. |
| One judge reports it | Record suspect; do not auto-fix. |
| Judges contradict | Escalate for explicit human decision. |
| Scoped re-judgment fails before round two | Parent may launch the final bounded fix round. |
| Any issue remains after round two | Escalate and stop. |
Execution Steps
- Build the complete immutable target and freeze the scope both judges will inspect.
- Launch both read-only judges in parallel (
jd-judge-a,jd-judge-b) against the same immutable target. - Merge findings into the frozen ledger and persist it through the selected artifact store.
- Ask before round-one correction; run the fix actor (
jd-fix-agent) only for confirmed severe IDs. - Run both judges again (
jd-judge-a,jd-judge-b) only over the frozen ledger plus immutable fix delta. - Repeat once at most, then run independent final verification and return the terminal verdict.
Output Contract
Return target identity, round, confirmed/suspect/contradiction/INFO counts, correction work units, scoped re-judgment result, artifact references, skill resolution, and exactly one final JUDGMENT: APPROVED ✅ or JUDGMENT: ESCALATED ⚠️.
References
- references/prompts-and-formats.md — compact judge/fix prompts and verdict shape.
- ../_shared/review-ledger-contract.md — delivery-authority route only: consult it when the caller explicitly opts into the ordinary negotiated review lifecycle; never required to run judges.
Version History
-
35deba3
Current 2026-08-20 00:47
移除对交付回执机制的依赖，使审查可在无回执保障的环境中运行；明确区分审查与发布权限；绑定子代理类型。
- e01b114 2026-07-25 06:59
