Read before you claim
Stop confident-but-wrong answers about unread code.
Official basis Minimize hallucinations — you MUST read the file before answering. docs ↗
The prompt
Read <file> in full before you answer. Never speculate about code you haven't opened — if you need another file to be sure, open it first, then explain what's wrong.Why it works
The official agentic-coding guidance is blunt: never speculate about code you have not opened. Making “read first” an explicit rule cuts the plausible-sounding guesses that waste a debugging session.
Fill in
<file>— the file the answer depends on.
Follow-ups
- “Which other files does this one depend on? Open them before concluding.”