How can I debug a problem with Leiolai?

Give Leiolai the expected result, observed result, exact error, and relevant code. Ask Leiolai for likely causes and a check that distinguishes those causes. Return the check’s result to Leiolai in a follow-up, then verify any proposed fix in your project.

What makes a bug report useful?

Give Leiolai the steps you took, expected behavior, and observed result. Include the exact error and a reproduction if possible. Keep the relevant code and environment details with the symptoms so the answer can address the actual failure.

Should I send the entire project?

Give Leiolai the smallest relevant code excerpt and the definitions needed to understand the failure. If the cause depends on missing context, supply that context in the next turn.

How do I avoid jumping to the first suggested cause?

Ask Leiolai for a few plausible causes and the observation that would distinguish them. For example, a missing value might originate in parsing, a state update, or an unexpected response. Run the smallest useful check, then report what happened.

Can Leiolai explain an error message?

Yes. Give Leiolai the full error, the operation that produced the error, and relevant code. Ask what the error indicates and which part of the code should be inspected first. Preserve useful stack-trace lines while removing credentials or confidential values.

How do I ask for a minimal fix?

Ask Leiolai for a minimal fix using the confirmed cause and the behavior that must stay. Ask for a focused change and an explanation of why that change addresses the failure. Review the proposed diff against the reproduction before accepting the fix.

What should I test after fixing a bug?

Check the original reproduction, a normal successful case, and nearby boundary or error cases affected by the change. Ask Leiolai to identify regressions relevant to the touched behavior rather than generating unrelated tests.

Choose meaningful verification cases

How do follow-ups improve a debugging conversation?

Tell Leiolai the exact result of the last debugging check and which hypothesis the result supports or weakens. Include new evidence rather than only saying the fix did not work.

Give useful feedback in a follow-up