When a program fails, a large replacement code block can hide the original problem. Begin by understanding the error and reproducing it with the smallest relevant example.
A practical way to start
Copy the exact error text, the relevant code and the action that triggered it. Remove tokens, passwords and private paths. State the language and environment details that you know.
Prompt to try
Explain this error in beginner language. Identify the line most likely involved and suggest the smallest change to test first. Do not rewrite unrelated code. If more context is needed, ask for it. Error: [message]. Relevant code: [code]. Expected behaviour: [description].
Check the result
Save your current work before applying a change. Run the same failing case again, then test a normal case. If the error changes, record the new message rather than stacking several unverified fixes.
Ask for a brief explanation of why the fix works. The aim is to build a troubleshooting habit you can repeat, not just collect snippets that happen to run once.