> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usejina.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompt Guide

> Trigger simulations and control scope, reruns, and depth.

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

```text PR comment theme={null}
@usejina "happy paths only"
```

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:

```text PR comment theme={null}
@usejina Focus on payment retries after a timeout. Check for duplicate charges.
```

Jina might reproduce a timeout and retry, then report the resulting payment state.

```text PR comment theme={null}
@usejina Check expired sessions. Include the request conditions and response.
```

Jina might exercise the endpoint and report its response, or explain what prevented execution.

Guidance applies to this run. Use [Customize Jina](https://docs.usejina.com/simulations/customize-jina.md) for durable preferences.

## Start fresh

```text PR comment theme={null}
@usejina /fresh Focus on checkout and refund consistency.
```

`/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:

```text PR comment theme={null}
@usejina /rerun
```

`/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:

```text PR comment — replace the example URL theme={null}
@usejina /rerun https://github.com/OWNER/REPO/pull/123#issuecomment-456
```

The link must point to a Jina Simulations comment on the same PR. Additional prose does not redefine the scenario set.

| Situation | Next step |
| - | - |
| No completed simulation with scenarios | Start one with `@usejina`. |
| No new commits since the last completed run | Push changes before rerunning. |
| A rerun is already running | Wait for it to finish. |

## Set depth for one run

```text PR comment theme={null}
@usejina /depth 3 Focus on retries and webhook delivery.
```

`/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:

```text PR comment theme={null}
@usejina /fresh /depth 3 Focus on retry safety.
```

| Combination | Result |
| - | - |
| `/fresh /depth 3` or `/depth 3 /fresh` | New investigation, up to three rounds. |
| `/fresh /rerun` | Invalid: fresh investigation and rerun cannot be combined. |
| `/rerun /depth 3` or `/depth 3 /rerun` | Invalid: reruns use one round. |
| `/depth 2 /depth 3` | Invalid: specify depth once. |
| `/depth 0`, `/depth 6`, `/depth 1.5` | Invalid: use an integer from `1` to `5`. |

Invalid combinations do not start a run. `@usejina investigate retries /depth 3` does not set depth because the command follows prose.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.