Most AI fixes fail because the report is missing the one thing the fix depends on: what you expected, what actually happened, and how to reproduce it.
https://www.notvibescoded.com/articles/bug-report-ai-can-fix
A usable bug report has three sentences. First, what you expected, specifically: "Clicking Save on the settings page should update the display name and show a confirmation." Second, what actually happened: "Clicking Save reloads the page, the display name is unchanged, and no confirmation appears." Third, how to reproduce it, the shortest path from a fresh state to the bug, including any condition that makes it happen or not happen.
Include the error, not your theory about it. Paste the full error message, plus ten lines before it for context, and stop there. A thousand lines of log is almost as useless as no log at all. Your theory can be wrong. The log cannot be misquoted if it is right there.
Keep it to one bug per report. Bundling three bugs into one prompt means the assistant fixes the first, half fixes the second, and silently drops the third. Split them, and each fix has one thing to get right and one way to check it.
Finally, say what "fixed" looks like: "Fixed means the steps above now produce the expected behaviour." That stops the assistant declaring victory after changing code that merely looks related, and it gives you a thirty-second test to run before merging.
The full piece, including a reusable template and what to leave out of a report, is on NotVibesCoded.
https://www.notvibescoded.com/articles/bug-report-ai-can-fix