Skip to main content
Jina validates findings against the code and investigation evidence before grading them. It considers impact, likelihood, affected functionality, evidence strength, and unresolved limitations.

​
Issue severity

Each validated issue receives a severity:

​
Pull-request merge score

The 1–5 score is a holistic assessment of the PR’s remaining merge risk. It is not a count of issues or an average of scenario scores. For example, an ordinary retry that duplicates a payment could warrant 2/5; a minor display defect could warrant 4/5. These are illustrative, not fixed mappings. Severity alone does not determine the PR score. Scenarios have execution results and findings, not numeric grades. A failed or blocked investigation is not a pass; read its limitations alongside the score.

​
Customize the rubric

Use .jina/instruction.md to describe how your product’s risks affect grading. For example:
.jina/instruction.md
You can customize the interpretation, but severities remain P0–P3 and PR scores remain integers from 1 to 5. Instructions cannot override evidence requirements. The file is read from the PR’s base commit. Use the setup prompt to choose repository-specific preferences.