Stage 6 · Lesson 2 of 6
Giving the tool full evidence
Give the tool the full error message, the (the list of function calls running when the error happened), relevant logs, the input, what you expected, what happened and what you already tried. Do not summarise in your own words: the detail you think is irrelevant is often the answer.
In , start a line with ! to run a command so its output joins the conversation, or pipe a log in with cat server.log | claude -p "...". In Cursor, @Terminals attaches terminal output. In Copilot chat, @terminal asks about the terminal and /fix proposes a fix for selected code.
Include versions of the language and key libraries when the bug might be version-specific.
Common trapsending half the stack trace and a paraphrase, then spending three rounds supplying what was missing.
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with
- CourseFreeThe Missing Semester of Your CS Education
MIT · Beginner
MIT's free lecture on debugging and profiling covers logging, debuggers and tools you will use for years