Configure reviews with .jina

Supported structure

Create only the files you need. Jina reads these files from the pull request’s base branch, so a pull request cannot change the instructions governing its own review.

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

Runtime depth

The optional depth setting accepts an integer from 1 through 5 and controls the maximum investigation loops. Reviews stop early when no follow-up areas remain. The default is 2.

{
  "depth": 2
}

Instruction precedence

1. Jina’s default stage prompt defines normal behavior and output contracts.
2. .jina/instruction.md adds repository-wide priorities and policy.
3. The matching stage instruction overrides conflicting global guidance for that stage.
4. Authorized run-specific instructions can focus one review.
5. Evidence, truthfulness, sandbox safety, and output contracts remain fixed.

Example repository policy

# Repository review policy

Prioritize tenant isolation, backwards-compatible API behavior,
and data-loss risks.

Ignore formatting concerns unless they demonstrate a production
behavior failure.

Limits

• Each instruction file contributes at most 8,000 characters.
• Files over 256,000 bytes are skipped.
• The combined global and stage appendix is capped at 24,000 characters.
• Missing and empty instruction files are ignored.
• Model selection remains an organization setting in the dashboard.