LESSON 03 OF 03 · WRITTEN GUIDE
Debug without guessing
A bug report should describe evidence rather than a theory. “The app is broken” forces the next person or model to guess. The useful report states what you did, what you expected, what happened, and whether it happens every time.
Make it practical
Reproduce one issue. Record the exact steps, the observed message, and the smallest input that triggers it. Remove sensitive values before sharing logs. Ask for an explanation before accepting a patch.
TRY THIS PROMPT
When I save a blank note, the old note returns after reload. Expected: the note stays empty. Actual: the old text returns. Here is the relevant save and load code. Identify the cause, propose a minimal fix, and describe a regression check.
Check your work
Does the fix address the observed cause? Does the original reproduction now pass? Have you checked the nearest related case?
Use the output as a draft. Compare it with the brief, inspect the work, and keep the decisions you can explain.