Customize reviews with .jina

Start with one instruction

Most repositories only need .jina/instruction.md. State the risks that matter, noise to ignore, and evidence required before Jina reports a finding.

# Review policy

## Prioritize
- Cross-tenant authorization failures.
- Data loss, duplicate effects, and unsafe retries.
- Backward-incompatible APIs.

## Ignore
- Style and naming without a behavior failure.

## Evidence
- Identify the triggering input and affected path.
- Prefer an executable reproduction.

Supported files

• instruction.md — priorities shared by every review stage.
• planner/instruction.md — repository-specific risk-area selection.
• replanner/instruction.md — useful follow-up criteria.
• investigation/instruction.md — safe commands, fixtures, and proof standards.
• review/instruction.md — severity and publication policy.
• config.json — investigation depth from 1 through 5.

.jina/
├── config.json
├── instruction.md
├── planner/instruction.md
├── replanner/instruction.md
├── investigation/instruction.md
└── review/instruction.md

Trust boundary

Review policy is loaded from the trusted base commit, so a pull request cannot redefine the policy used to review itself. Evidence, output schemas, sandbox safety, and truthfulness requirements cannot be overridden.

Roll out a policy change

1. Change .jina files in a pull request so policy is reviewed like code.
2. Expect that pull request to use the previous base policy.
3. Merge the change, then evaluate it on a later review.
4. Change one dimension at a time and compare quality, latency, and cost.