Evidence-first pull request review with independent critique, selective challenger review, and human handoff.
87
92%
Does it follow best practices?
Impact
87%
1.31xAverage score across 43 eval scenarios
Risky
Do not use without reviewing
{
"context": "Cascading: ECS task and Helm resource limits slashed 4x for a production payments service — will cause OOM kills and cascading restarts under load",
"type": "weighted_checklist",
"checklist": [
{
"name": "Catches dangerous resource reduction",
"description": "Identifies that cutting memory limits from 2048MiB to 512MiB (4x reduction) for a production payments service is dangerous — normal traffic spikes or memory-intensive operations will trigger OOM kills",
"max_score": 12
},
{
"name": "Identifies cascading restart risk",
"description": "Recognizes that OOM-killed containers trigger restarts, which shift load to remaining instances, which are also resource-constrained, leading to a cascading failure across the fleet",
"max_score": 8
},
{
"name": "Risk classified yellow or higher",
"description": "PR touches production resource limits for a payment-critical service and should be classified as at least yellow risk",
"max_score": 10
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
rules
skills
challenger-review
finding-synthesizer
fresh-eyes-review
human-review-handoff
pr-evidence-builder
review-retrospective