judge-dredd

Reviews task diffs and evidence to approve or return kanban tasks at yolo workflow gates.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill judge-dredd-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: judge-dredd
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/judge-dredd
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill judge-dredd-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous task workflows need an independent quality gate that decides whether completed work actually meets the original request, without re-running tests or expanding scope. This Skill acts as the single judge at the closing gate of every yolo task and at the planning gate of critical tasks, keeping human approval focused where it matters. ## Core Features & Use Cases - Gate-based judgment: Operates at the 005_closing gate of every yolo task and the 003 gate of critical tasks, always in a fresh context separate from planners and executors. - Materiality-filtered findings: Every objection must pass a five-question materiality test with verifiable evidence, severity, and remedy before it can block a task. - Structured verdicts and deltas: Produces a .verify.md verdict with machine-readable markers and, on returns, a delta classifying the defect as directed repair, execution failure, plan gap, or wrong premise. - Use Case: An orchestrator finishes an autonomous coding task and invokes this Skill to audit the integrated diff against the card's objective; the judge approves with a memory entry or returns the task to the correct stage with a precise delta. ## Quick Start Ask the agent to act as judge-dredd and judge the task at its 005_closing gate by reading the card, plan, and integrated diff, then write the verdict in the .verify.md file.

Frequently Asked Questions about judge-dredd

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

FAQPage Schema
How do I add a quality gate to an autonomous AI coding workflow?▼

Use a dedicated judge subagent that runs in a fresh context at the closing gate of each task. It reads the card objective, specs, and integrated diff, then issues an approval or a classified return without re-running tests.

How does the judge decide whether a task passes or returns?▼

It first checks whether the card's original request was met, then audits the diff in one pass. Every finding must pass a five-question materiality test with verifiable evidence, and returns are classified as directed repair, execution failure, plan gap, or wrong premise.

Does the judge re-run tests to verify completed work?▼

No, the judge decides by reading the diff and recorded evidence only. The sole exception is a test-versus-code dispute, where it runs only the single disputed test file and attaches the result as evidence.

What happens when a task keeps failing the same gate?▼

Return counters track each route, and after two returns of the same type the judge stops returning and sets a circuit breaker flag requesting human intervention instead of looping indefinitely.

Can the judge fix defects it finds during review?▼

No, the judge never fixes code, edits card frontmatter, integrates branches, or moves task folders. It only names the delta in its verdict; the orchestrator dispatches any correction.