Evidence-first pull request review with independent critique, selective challenger review, and human handoff.
89
92%
Does it follow best practices?
Impact
89%
1.36xAverage score across 43 eval scenarios
Risky
Do not use without reviewing
{
"context": "Cascading: default payment provider is 'braintree' but only 'stripe' is registered — every payment call crashes if PAYMENT_PROVIDER env var is unset",
"type": "weighted_checklist",
"checklist": [
{
"name": "Catches default provider mismatch",
"description": "Identifies that DEFAULT_PROVIDER defaults to 'braintree' but PROVIDERS only contains 'stripe', so if the PAYMENT_PROVIDER env var is not set, provider lookup returns None and instantiation crashes with TypeError",
"max_score": 15
},
{
"name": "Identifies total payment outage impact",
"description": "Recognizes that this is not a minor config issue but a total payment system outage — every create_charge and refund_charge call will fail if the env var is missing",
"max_score": 8
},
{
"name": "Risk classified red",
"description": "PR is classified as red due to payment-critical code path that crashes under a common deployment configuration",
"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