existential-birds/beagle / plugins/beagle-analysis/skills/llm-judge
llm-judge
VerifiedUse when comparing two or more code implementations against a spec or requirements doc. Triggers on "which repo is better", "compare these implementations", "evaluate both solutions", "rank these codebases", or "judge which approach wins". Also covers choosing between competing PRs or vendor submissions solving the same problem. Does NOT review a single codebase for quality — use code review skills instead. Does NOT evaluate strategy docs — use strategy-review. Requires a spec file and 2+ repo paths.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.7 KB |
| references/fact-schema.md | markdown | 4.3 KB |
| references/judge-agents.md | markdown | 2.7 KB |
| references/repo-agent.md | markdown | 3.1 KB |
| references/scoring-rubrics.md | markdown | 4.1 KB |
references/fact-schema.md
View on GitHub# Fact Schema
JSON schema for structured facts gathered by Phase 1 Repo Agents.
## Full Schema
```json
{
"repo_label": "string - Display name for this repo",
"repo_path": "string - Absolute path to repo",
"git_info": {
"branch": "string - Current branch name",
"base": "string - Base branch (usually main)",
"files_changed": "number - Count of changed files",
"additions": "number - Lines added",
"deletions": "number - Lines deleted",
"diff_summary": "string - Brief description of changes"
},
"functionality": {
"spec_requirements": ["array of requirement strings extracted from spec"],
"implemented": ["array of requirements found implemented"],
"missing": ["array of requirements not found"],
"partially_implemented": ["array of requirements with incomplete implementation"],
"test_results": {
"ran": "boolean - Whether tests were executed",
"framework": "string - pytest, jest, go test, etc.",
"passed": "number",
"failed": "number",
"skipped": "number",
"error_summary": "string - Brief description of failures if any"
}
},
"security": {
"findings": [
{
"file": "string - File path",
"line": "number - Line number",
"issue": "string - Description of security issue",
"severity": "high | medium | low",
"category": "string - OWASP category if applicable"
}
],
"patterns_observed": ["array of positive security patterns found"]
},
"tests": {
"test_count": "number - Total test count",
"coverage_estimate": "none | low | moderate | high",
"dry_violations": [
{
"file": "string",
"line": "number",
"description": "string"
}
],
"mocking_approach": "string - Description of mocking strategy",
"test_quality_notes": "string - General observations"
},
"overengineering": {
"abstractions": [
{
"file": "string",
"line": "number",
"issue": "string - Description of over-abstraction"
}
],
"defensive_code": [
{
"file": "string",
"line": "number",
"issue": "string"
}
],
"config_complexity": "low | medium | high"
},
"dead_code": {
"unused_imports": ["array of file:line references"],
"unused_functions": ["array of file:line references"],
"unused_variables": ["array of file:line references"],
"todo_comments": "number - Count of TODO/FIXME",
"commented_code_blocks": "number - Count of commented code"
}
}
```
## Example
```json
{
"repo_label": "Claude",
"repo_path": "/path/to/repo-a",
"git_info": {
"branch": "main",
"base": "main",
"files_changed": 42,
"additions": 1250,
"deletions": 380,
"diff_summary": "Adds auth flow and data export features"
},
"functionality": {
"spec_requirements": ["auth flow", "data export", "rate limiting"],
"implemented": ["auth flow", "data export"],
"missing": ["rate limiting"],
"partially_implemented": [],
"test_results": {
"ran": true,
"framework": "pytest",
"passed": 45,
"failed": 2,
"skipped": 1,
"error_summary": "2 tests fail on edge case validation"
}
},
"security": {
"findings": [
{
"file": "src/api.py",
"line": 42,
"issue": "SQL string concatenation instead of parameterized query",
"severity": "high",
"category": "Injection"
}
],
"patterns_observed": ["input validation present", "no secrets in code", "HTTPS enforced"]
},
"tests": {
"test_count": 48,
"coverage_estimate": "moderate",
"dry_violations": [
{
"file": "tests/test_api.py",
"line": 15,
"description": "Setup code repeated in 5 test functions"
}
],
"mocking_approach": "Mocks at adapter boundary, uses pytest fixtures",
"test_quality_notes": "Good isolation, some DRY issues"
},
"overengineering": {
"abstractions": [
{
"file": "src/factory.py",
"line": 1,
"issue": "Factory pattern for single implementation"
}
],
"defensive_code": [],
"config_complexity": "low"
},
"dead_code": {
"unused_imports": ["src/utils.py:3"],
"unused_functions": [],
"unused_variables": [],
"todo_comments": 2,
"commented_code_blocks": 1
}
}
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |