scaffold_judge
Generate boilerplate files for a new judge: definition, evaluator skeleton, and index.ts line. Validates uniqueness of judge ID and rule prefix.
Instructions
Generate the boilerplate files to add a new judge to the Judges Panel. Creates the judge definition (with self-registration), evaluator skeleton, and tells you the one line to add to index.ts. Validates that the judge ID and rule prefix are unique.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Unique kebab-case judge identifier (e.g., 'supply-chain', 'code-review') | |
| name | Yes | Human-readable judge name. Must start with "Judge " (e.g., "Judge Supply Chain") | |
| domain | Yes | Expertise area (e.g., "Supply Chain Security") | |
| dryRun | No | If true, preview the generated files without writing to disk (default: false) | |
| rulePrefix | Yes | Uppercase prefix for rule IDs (e.g., "SCS"). Must be unique across all judges. | |
| description | Yes | One-sentence summary of what this judge evaluates | |
| samplePatterns | No | Example code patterns the evaluator should detect (strings or regex snippets). Used to seed the evaluator with starter detection logic. | |
| tableDescription | Yes | Comma-separated keywords for the README table (e.g., "Dependency provenance, SBOM, build integrity") | |
| promptDescription | Yes | Short action phrase for the prompts table (e.g., "Deep supply chain security review") | |
| evaluationCriteria | No | List of evaluation criteria / categories to include in the system prompt (e.g., ['Dependency provenance', 'Build integrity']) |