new-skill

Explain Error

When the user shares an error message or stack trace:

1. Identify the error type — What category of error is this? (syntax, runtime, type, network, permission, etc.)
2. Explain in plain English — What does this error actually mean? Avoid jargon.
3. Find the root cause — Look at the stack trace to identify where and why it failed.
4. Suggest a fix — Give a concrete code change or action to resolve it.
5. Explain how to prevent it — What pattern or practice avoids this in the future?

Keep explanations concise. Lead with the fix, follow with the explanation.