Skip to content

Reviewing a run

A run is everything Lyzentra did for one issue. Open it from Runs, from the job, or from the issue's Latest run. The Overview tab has what you need to decide whether to publish.

Task

The Task section shows what Lyzentra understood: the goal, the acceptance criteria and the files it expects to touch.

The score next to it (0 to 100) is how well the issue can be built without guessing. 80 and up means the issue is clear. 50 to 79 means Lyzentra filled small gaps with sensible defaults; check the acceptance criteria. Below 50 it usually asks on the issue instead of coding.

The size is S, M, L or XL. XL means the change is too big for one pull request, and the section suggests how to split the issue.

Proof of work

The Proof of work section is the summary a reviewer needs, and the pull request contains the same information:

  • Tests: how many ran, whether the build passed and how long it took.
  • Change: files changed and lines added and removed, per file.
  • Security review: anything suspicious in the added lines, with its risk.
  • AI review: the model's review of the change, with findings on specific lines.
  • Attempts: 1 means the build passed the first time; more means Lyzentra had to fix its own change.
  • Model work: tokens and model time.

A high-risk security finding stops the run from being published automatically. Look at the lines it points to before you publish by hand.

Other tabs

  • Build log: the end of the build output.
  • Changes: every changed file, side by side with the original.
  • Repository context: what the model was shown about your repository.

CI

Once the change is published, the CI section shows your repository's own checks for the pull request, with Fix failing CI when one fails. See Pull requests.

Trying the change

Live preview starts the code as a temporary test app and gives you a link. It also checks the home page and any URL named in the acceptance criteria.

From the Preview section you can stop it, start it again without rebuilding, rebuild it or remove it. Previews stop by themselves after two hours and are removed a day after that. If a preview fails, Fix these errors passes the failure to Lyzentra.

Previews depend on the server. If the section says previews are turned off or not available, ask your administrator.