Explain an unfamiliar function before editing it
Understand a small code snippet, its assumptions, and the questions to answer before changing it.
Make the behavior understandable before making a change. Work with a small code sample, a clear bug report, or a prototype using dummy data, and keep executable checks separate from plausible explanations.
Understand a small code snippet, its assumptions, and the questions to answer before changing it.
Organize known facts, competing explanations, and the smallest useful checks before changing code.
Use Gemini Canvas to explore an interface before connecting accounts or building a production app.
Use code you are entitled to share and remove secrets, credentials, and private data. Include only the context needed to understand the behavior.
No. Compare the explanation with the code and run appropriate checks in your own environment. A suggested fix or prototype remains unverified until you test it.
Record the environment, smallest known reproduction steps, expected result, actual result, and evidence. Label guesses about the cause as guesses.