Jev Review Workflow
A staged code-review workflow follows Jev signals through focused checks and a local dashboard.
Added to Jevfast
How it uses Jev
Jev evaluates bounded review questions over a Git diff or codebase scan. Ordinary orchestration follows risk signals through focused file and change judgments, then assembles the report.
What Jev decides
Check runtime correctnessExample answers · not a recorded Jev response · Source ↗
Question 1 · correctness
YOUR APP
INSTRUCTION
Does this source region directly support that the code contains incorrect runtime behavior?
STATE
One bounded source region from a file, with its path and starting line, plus related tests selected by the workflow.
JEV · NOUL
YesNo
App workflow
- Load review target
Load a Git diff or collect a codebase snapshot.
- Classify review signals
Ask Jev for initial risk signals and file profiles.
- Inspect focused areas
Run focused follow-up judgments on the strongest signals.
- Present the report
Save the review result and present it in the local dashboard.
Why it is interesting
The code stages risk screening, file profiling, evidence selection, issue classification, severity scoring, and conditional reviewer routing, with thresholds applied by the workflow.