Skip to main content
A manual trigger is a new PR conversation comment or inline review comment mentioning @usejina. Jina must be enabled for the repository, and you need write, maintain, or admin access.

​
Start a simulation

PR comment
This focuses the run on successful use of the changed behavior. For a checkout change, Jina might check that a purchase completes and the order and payment state agree. This is an illustrative output, not evidence that failure paths were tested. Use @usejina alone for a review without extra guidance. Quotes are optional. Post a new comment to trigger another run; editing an existing comment does not start one.

​
Steer the investigation

Describe the scope or evidence you want. These are illustrative examples:
PR comment
Jina might reproduce a timeout and retry, then report the resulting payment state.
PR comment
Jina might exercise the endpoint and report its response, or explain what prevented execution. Guidance applies to this run. Use Customize Jina for durable preferences.

​
Start fresh

PR comment
/fresh starts a new investigation without prior PR conversation or inherited inline-issue scope. Repository context and preferences still apply.

​
Rerun after pushing fixes

Push new commits, then comment:
PR comment
/rerun replays the existing scenario set in one round. The updated Jina Simulations comment reports issues as fixed, still open, or not verified, plus any new findings within that scope. By default, it targets the latest simulation. To choose another, place its comment link immediately after the command:
PR comment — replace the example URL
The link must point to a Jina Simulations comment on the same PR. Additional prose does not redefine the scenario set.

​
Set depth for one run

PR comment
/depth 1 through /depth 5 set the maximum investigation rounds for this run. Jina can stop earlier when no useful follow-up remains. An explicit command overrides .jina/config.json at the PR’s base commit. Without either, the default is 2.

​
Combine commands and guidance

Put commands before natural-language guidance:
PR comment
Invalid combinations do not start a run. @usejina investigate retries /depth 3 does not set depth because the command follows prose.