How Jina reviews code
The stages, evidence model, severities, and merge-readiness contract behind a review.
Review stages
- Planner identifies materially affected runtime surfaces and concrete failure modes.
- Investigation agents inspect and execute the code in isolated sandboxes.
- Replanner adds evidence-driven follow-up work when another investigation loop is useful.
- Reviewer validates, deduplicates, assigns severity, and determines merge readiness.
Severity
- P0 — critical and must be fixed before merging.
- P1 — high impact and should be fixed.
- P2 — medium impact and worth fixing.
- P3 — low-priority but concrete behavior problem.
Evidence
A useful finding identifies a specific behavior failure, the conditions that trigger it, and the relevant source location. Execution-backed evidence is preferred when the behavior can be exercised safely.
The dashboard retains investigation detail even when a candidate is dismissed during final validation.