Can Leiolai help review a code change?
Yes. Ask Leiolai to review your code diff for concrete bugs. Provide the surrounding code, intended behavior, and project constraints. Request a trigger and consequence for each finding, then verify the findings against your project.
Read the Leiolai prompting guide
What context should accompany a diff?
Give Leiolai the problem the diff solves and the expected behavior. Supply surrounding code that affects the changed path, plus relevant contracts or tests.
What should a useful finding include?
Ask Leiolai for the location, triggering condition, consequence, and evidence in the code. For example, a finding about an empty list should explain how that input reaches the branch and what fails.
Can I focus a review on one risk?
Yes. Ask Leiolai to examine a specific risk in the diff, such as error handling, state transitions, resource cleanup, or an empty input. Supply the surrounding code and ask for the trigger and consequence of any finding.
How do I separate bugs from style preferences?
Ask Leiolai for behavioral bugs with a trigger and consequence. Request optional readability suggestions separately. Supply the project’s established conventions so the review can use them.
Can Leiolai help explain why a patch works?
Yes. Ask Leiolai for the before-and-after behavior under the original trigger. Request which part of the change prevents the failure and what assumption the fix relies on. Compare that explanation with the actual code and reproduction.
How do I verify a proposed finding?
Verify a Leiolai code-review finding by reproducing the trigger or checking the affected behavior. If the finding depends on an external API contract, confirm that contract. Use the evidence to decide whether the patch needs a correction.
Plan checks for a code changeCan I use the review to write a clear change description?
Yes. Ask Leiolai for a description of the problem, resulting behavior, and validation performed. Supply the checks that actually ran so the description does not invent test results.
Explain a technical change clearly