how it works

Connect a repository and hand VELIN a job, for example “check what the app does when the RPC stops responding.” Every step it takes becomes a tile on the map; click one to see the file it read, the command it ran, or the change it proposed.

1. 01

   inspect

   Reads the code the report points at and finds the project's test setup.

2. 02

   run

   Runs the existing tests in a throwaway container with no network.

3. 03

   reproduce

   Writes a focused test that has to fail on the original code.

4. 04

   patch

   Proposes the smallest fix, then re-runs the same test and the whole suite.

5. 05

   report

   A verdict computed from exit codes, the patch, and a report. You review before anything is applied.

The demo on this page: a wallet dashboard stays on “loading” forever when an RPC request fails. VELIN reproduces it with a failing test, proposes a request timeout and a message for the user, and shows the same test before (failing) and after (passing).