CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/pr-review-guardrails

Evidence-first pull request review with independent critique, selective challenger review, and human handoff.

87

1.31x
Quality

92%

Does it follow best practices?

Impact

87%

1.31x

Average score across 43 eval scenarios

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-28/

{
  "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
    }
  ]
}

README.md

tile.json