JAIPilot / Verify

Verify your code before you ship it.

A testing agent that verifies your code. Run it after a change is made: Verify tests the new code, checks existing behavior for regressions, and lets you decide what should happen before it reports the result.

Watch the real run Install Verify

For changes made by you or your coding agent. Run Verify before you commit.

THE HANDOFF
Code change ready
Run Verify
Review the evidence

Baseline → intent → final tests → report

One change. One real run.

Watch Verify on Spring Petclinic.

A coding agent added kitty → cat and puppy → dog using a new resolver and a change to the existing formatter. Verify then checked the new behavior and whether the old behavior still held.

Captioned recording of a coding agent adding pet type aliases in Spring Petclinic, followed by Verify checking the baseline, asking about a missing target, testing the accepted change, and reporting good_to_go
Selected frames from a real local terminal run, with explanatory captions. Verify found an untested missing-target case; the review confirmed it should keep the original error. The final Maven tests and coverage checks passed. Open demo at full size ↗ · Run notes ↗

How it works

A review between coding and committing.

Verify works from your Git change. It keeps the baseline and candidate in separate worktrees, so you can inspect the result before accepting edits.

  1. 01

    Establish the baseline

    Verify tests affected behavior before your change, then replays those tests against the code you wrote.

  2. 02

    Review what changed

    It separates intended changes from possible regressions, asks when intent is unclear, and previews proposed edits.

  3. 03

    Lock the agreed behavior

    After you accept the candidate, Verify adds tests for the new behavior and runs the project suite and coverage checks.

  4. 04

    Read the evidence

    Get a verdict, the test and coverage results, and the complete verified diff before choosing whether to apply it.

Passing checks show the behavior they exercised. They do not prove that every possible bug is gone. Read the detailed workflow ↗

Get started

Run Verify before you commit.

Install the standalone CLI, then run it inside the Git repository that contains your change. Verify uses your JAIPilot sign-in and your project’s local build, test, and coverage tools.

01

Install on macOS or Linux

curl -fsSL https://raw.githubusercontent.com/JAIPilot/verify/main/install.sh | sh

The installer checks the release checksum and places verify in ~/.local/bin.

02

Install on Windows

irm https://raw.githubusercontent.com/JAIPilot/verify/main/install.ps1 | iex

Run in PowerShell. Open a new terminal after installation so the updated user PATH is available.

03

Run it in your project

verify auth login
verify

Have Git and your project’s build, test, and coverage tools ready. Verify shows questions and proposed edits for your review.

Download the latest release ↗ Explore the GitHub repository ↗

Local execution / user review

See the work. Decide on the diff.

Builds, tests, and file edits run in local worktrees. Verify sends the relevant diff, requested file contents, and command output to JAIPilot and its model provider. You review proposed edits and choose whether to apply the final verified diff.