Skip to main content

​
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:
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:
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

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

​
Cancel a run

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.
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.
  • 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.

​
Next steps

Run a validation tutorial · Read the validation spec · Use the API