Day 06 of 21
How to read error messages without panicking
Goal: Error messages look catastrophic. They are not. Today you learn the one part of every error message that actually matters — and how to hand it to Claude Code to fix in seconds.
What to do
Create a practice branch
Open GitHub Desktop and create a branch called "day-6-error-practice". This keeps any intentional errors away from your working code.
Ask Claude Code to introduce a small deliberate error
Open Claude Code in your project. Ask it:
Introduce a small deliberate error into one file on this project — something that will produce a visible error message. Tell me which file you changed and what the error will be.Find the last two lines of the error
When the error appears — scroll to the very bottom of the red text. The actual error is almost always in the last two lines. Everything above is just the trail that led to it.
Give the error to Claude Code to fix
Copy the last two lines of the error. In Claude Code, type:
I got this error. Please fix it: [paste the last two lines here]Expected result
You intentionally introduced an error, found the important part of the error message, handed it to Claude Code, and watched it fix the error in seconds.
Key takeaway
- Scroll to the bottom of the error. Copy the last two lines. Paste them into Claude Code with "I got this error. Please fix it." That is the entire process — every time.