Commit message check
Does the commit message match the staged diff, with no secrets or debug leftovers?
A pre-commit or CI check: the message has to describe what the diff actually does, significant unmentioned changes are flagged, and secrets or debug leftovers block the commit.
Try it live
Real calls to Jev. Pick an example or paste your own.
Pick an example or paste your own input, then run it.
Under the hood
Every question and rule, in the open. Fork it to change any of them.
What it asks
Reads message and diff, then asks 5 questions in one call.
- Q1Message matchesYes / no
Does the commit
messageaccurately describe what thediffchanges? - Q2Unmentioned changesYes / no
Does the
diffinclude a significant change themessagedoesn't mention? - Q3Debug leftoversYes / no
Does the
diffadd debug output, commented-out code or temporary hacks? - Q4SecretsYes / no
Does the
diffadd a password, API key, token or private key? - Q5TypePick one
What kind of change is this?
FeatureFixRefactorDocsTestsChorePerformanceOther
How it decides
Rules run in code, top to bottom. The first one that matches gives the verdict.
- 1If Secrets ≥ 0.6Block
- 2If Message matches < 0.4Amend
- 3If Unmentioned changes ≥ 0.6Amend
- 4If Debug leftovers ≥ 0.7Amend
- ·DefaultLooks good
Call it from your code
Every template runs as-is with an API key, no setup: POST /api/v1/judges/commit-check/run.
curl -X POST https://tryevally.com/api/v1/judges/commit-check/run \ -H "Authorization: Bearer $EVALLY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "input": { "message": "Fix typo in README", "diff": "--- a/README.md\n+++ b/README.md\n-Instalation\n+Installation\n--- a/src/config.ts\n+++ b/src/config.ts\n+export const STRIPE_KEY = '\''sk_live_51Hc9fake0000EXAMPLE'\'';" }}'Seen in the wild
Community builds on Jev that use this pattern. Not affiliated with Evally.
More in Engineering
- Engineering
PR risk review
Is this pull request safe to merge, or does it need a careful human look?
Safe to mergeNeeds careful reviewChanges requested7 questions - Engineering
Semantic code lint
Lint code against conventions written in plain English, the rules a regex can't express.
CleanWarningsViolations5 questions - Engineering
PR labeler
Label pull requests by type and area, and flag what belongs in the changelog.
FeatureBug fixRefactor+64 questions - Engineering
Package risk check
Catch typosquats and hostile install scripts before an install runs them.
AllowReviewBlock7 questions - Engineering
Vulnerable code check
Flag injection, path traversal, hardcoded secrets and other common holes in a change.
CleanReviewVulnerable4 questions - Engineering
Judge question review
Review a question before Jev answers it: two judgments in one, inputs no option fits, a rating hiding in a yes/no.
Good to goImproveRewrite3 questions - Engineering
Should this be a judge?
Paste a prompt from your code. Find out whether it's really a decision a judge would answer faster and cheaper.
Use a judgeSplit itKeep the LLM4 questions