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

# Validate commands

> Request, revise, run, check, and cancel a validation from a GitHub pull request.

## Request or run a validation

Comment `@remyx-ai validate` on a connected pull request. If no spec is committed, Validate proposes a test for review. If a valid spec is already committed, the command can start execution.

A request that explicitly asks to revise and run can also skip a separate confirmation. Review the spec and any instructions that will trigger execution.

The command reference below lists supported actions, aliases, authorization rules, response states and cancellation behavior.

## Request a test

Comment on an open pull request:

```text theme={null}
@remyx-ai validate
```

If the PR has no validation spec, Validate proposes a test and commits the proposal to the PR branch for review. Add a description of what to measure when the default question is too broad.

## Run an approved test

After reviewing the proposal and `.remyx/validation.yaml`, comment again:

```text theme={null}
@remyx-ai validate
```

When a committed validation spec already exists, the command can begin the run without generating a proposal first.

## Revise a proposal

Use the documented `@remyx-ai revise` command to request a change to the proposed test or criteria.

Review the updated proposal before running it.

## Check progress

```text theme={null}
@remyx-ai status
```

Read the PR comment and the Remyx Validation GitHub Check for the latest state.

## Cancel a run

```text theme={null}
@remyx-ai cancel
```

Cancellation requests stop an in-flight validation and its repair loop. Review the resulting status before starting another run.

## Full command reference

The tables below list the supported aliases, comment-routing rules, and run-state behavior.

The handle is the App's slug, `@remyx-ai`. `@remyxai` and `@remyx` also work, in any case.

| You want to | Comment | What happens |
| - | - | - |
| **Start or confirm** | `@remyx-ai validate` | With a proposal waiting: confirms it and runs it, smoke test first. With a committed spec and no proposal: runs the spec. With neither: proposes a test from the PR itself. |
| **Start with your own ask** | `@remyx-ai validate <what to measure>` | Designs a test for that claim, commits it to the PR branch, and posts it for review. Nothing runs yet. |
| **Revise** | `@remyx-ai validate <feedback>` or `@remyx-ai revise <what to change>` on a proposed test | Revises the proposal from the previous attempt plus your feedback. Add "and run it" to run as soon as it is revised. `redesign` and `refine` also work. |
| **Check status** | `@remyx-ai status` | Where the run is and how long it has been going. |
| **Cancel** | `@remyx-ai cancel` | Stops the in-flight run and the fix loop behind it. `stop` and `abort` also work. |
| **Ask about a run** | `@remyx-ai <a question>` | Answered from the run's own telemetry, with no action on the validation. |

> [!NOTE]
>
> A committed `.remyx/validation.yaml` takes precedence over guidance in a new PR comment. To change its test or criteria, edit the file on the branch before you run. Comment feedback alone does not revise a hand-written spec.

> [accordion] Advanced routing behavior
>
> * **The bare commands never go to a model.** `validate`, `cancel`, `revise` and `status` on their own are matched literally and act immediately.
> * **Everything else is routed by a model** that reads the comment, the thread, and the PR's state (spec committed, proposal pending, run in flight) and picks one intent: propose, revise, run, cancel, status, question, or unclear. Below 0.5 confidence it asks you instead of guessing. If the model is unreachable, the literal commands are the fallback.
> * **Informal asks with an action verb** ("please run a validation vs the upstream benchmark") route to the same pipeline as `validate`. Questions about a validation go to Ask.
> * **Feedback on a proposal is routed as a revision.** If the request also explicitly asks to "and run it", the revised test can start immediately when the revision lands, without another approval comment. A `validate` comment that reports a change you already made (for example, "fixed the version pin") requests a run.
> * **Every reply ends with the next step** for the state the PR is in.

> [accordion] Who may trigger, caps, and acknowledgement
>
> | Rule | Value |
> | - | - |
> | Who may trigger | Comment authors whose GitHub association is `OWNER`, `MEMBER` or `COLLABORATOR`. Others are ignored and logged. |
> | Daily cap | 20 answered mentions per repo per day. |
> | Acknowledgement | A 👀 reaction on your comment. No reaction means the mention was ignored; the reason is in the engine log. |
> | One run per commit | A second `validate` on a commit already being measured points at that run. Push a new commit to measure that instead. |
> | One run per repo | A run in flight on another PR of the same repo refuses this one at start. Nothing is used. |

## Next steps

[Run a validation tutorial](https://docs.remyx.ai/tutorials/validate-first-run.md) · [Read the validation spec](https://docs.remyx.ai/platform/agents/validate-spec.md) · [Use the API](https://docs.remyx.ai/api-reference/validate.md)


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