> ## 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 a pull request

> Request a PR validation, review the test and inspect metrics, artifacts and cost.

Measure a change against defined criteria before merging it.

Validate proposes and runs an evaluation on a pull request in a connected GitHub repository. It works on PRs written by your team, another coding agent, or Outrider.

## Run a validation

1. Connect the repository through the Remyx GitHub App and enable Validations.
2. Comment `@remyx-ai validate` on an open pull request to request a test.
3. Review the proposed test and criteria. Confirm the run when the request requires a separate approval.
4. Inspect the measured results, executed notebook, and cost on the pull request.

A committed validation spec can start a run directly. An explicit request to revise and run may also skip separate confirmation.

[Run your first validation](https://docs.remyx.ai/tutorials/validate-first-run.md) · [Command reference](https://docs.remyx.ai/platform/agents/validate-commands.md)

![GitHub PR conversation showing an @remyx-ai validate request and the bot acknowledging that it is designing a proposed test.](https://mintcdn.com/remyxai/tTKg7dmpknqQ3oqG/images/docs/r4/validate-pr-request.png?fit=max\&auto=format\&n=tTKg7dmpknqQ3oqG\&q=85\&s=6143a1ef7ae742276e8143a3dd8ed3d2)

Request an evaluation directly from a GitHub pull request.

## What gets measured

Some validations compare the base branch with the PR. Others test a new capability against an absolute threshold or reference. The result identifies the comparison used and which criteria were met.

## See a completed result

The SAELens validation compared TopK and AbsTopK sparse autoencoders under two offline criteria. In the recorded single-seed CPU run, both criteria were met.

| Measure | TopK | AbsTopK |
| - | -: | -: |
| Explained variance | 0.9666 | 0.9677 |
| Negative selected latents | 0% | 49.2% |

![Validate's GitHub result for SAELens, with a passing verdict, parity-gap metric, negative-latent metric, and evidence table.](https://mintcdn.com/remyxai/tTKg7dmpknqQ3oqG/images/docs/r4/validate-sae-result.png?fit=max\&auto=format\&n=tTKg7dmpknqQ3oqG\&q=85\&s=4d1db7eb14a421f1a38a4f786f47a203)

The SAELens validation met both specified offline criteria in one CPU run.

This result supports the specified test criteria. It does not establish production improvement or downstream steering and monitoring performance.

[Read the GitHub result](https://github.com/salma-remyx/SAELens/pull/5) · [Open the notebook](https://github.com/salma-remyx/SAELens/blob/6989234239f49130fd1e77412f04a0513268fc87/.remyx/validations/abstopk-vs-topk-tinystories.ipynb)

## What changes on the PR

Validate commits proposed test files and configuration to the PR branch. Executed notebooks are committed by default. Automatic repair may also edit repository code by default, but cannot change the confirmed test or criteria.

[Execution and safeguards](https://docs.remyx.ai/platform/agents/validate-execution.md)

## Cost

The first completed eligible validation is free per GitHub App installation. Later completed runs use prepaid credits or an applicable grant. A valid inconclusive result may still count as a completed, chargeable run.

[Billing](https://docs.remyx.ai/platform/configure/billing.md) · [Results and evidence](https://docs.remyx.ai/platform/agents/validate-results.md) · [Compute and limits](https://docs.remyx.ai/platform/agents/validate-limits.md)


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