Find what's really broken before Lovable fixes it
Lovable identifies what caused the bug, not just a quick fix, when you ask in Plan mode.
When to use it
Your bug keeps coming back even after Lovable fixes it multiple times.
Why it is worth it
Understanding the real problem prevents the bug from creeping back in different forms later.
Before you start
- Click Try to fix when the error appears
- Describe what's broken with a screenshot or error message
Paste this into Lovable's chat on the project with that page.
The prompt
My checkout button stopped working after I added the new tax calculator feature. The button doesn't respond when clicked and no error appears in the console. Review your recent changes to the checkout flow component and related files. Identify which change broke the button interaction and explain what went wrong before proposing a fix. I need to understand why so we can prevent similar issues.
Swap the checkout button and tax calculator with what you changed in your app.
What you get
Lovable explains which change broke the button and how to fix it, so the same issue doesn't come back.
From docs.lovable.dev/prompting/prompting-debugging
