What this guide helps you do
A debugging assistant needs a reproducible problem more than a large code dump. State the language, runtime, expected behavior, and exact error. Gemini can help explain code and propose changes, but the proposed patch remains unverified until you run it in your environment. Keep the first request focused on locating the failure. Rewriting an entire application can replace a small understandable defect with several new ones.
A practical worked example
A contact form displays success even when its email operation fails. Provide the smallest relevant function, a sanitized error message, and an example request. Ask Gemini to explain where the response is chosen and propose a focused correction. The acceptance check should include a successful send and a simulated failure. Merely making the success message appear more attractive does not repair the incorrect behavior.
How to approach the task
Separate diagnosis, patch, and verification. Ask which observation supports the hypothesis and what test would disprove it. Review changes for surrounding behavior, especially validation and failure handling. Keep credentials out of sample code. When the error is fixed, save the reproduction and a short explanation so a future change can be checked against the same case. Use official language and framework documentation for uncertain API behavior.
Step-by-step workflow
- Record expected behavior and the exact failure.
- Reduce the code to a reproducible sanitized example.
- Ask for an explanation and a minimal patch.
- Test success, failure, and invalid input.
- Review the change and retain the reproduction.
Reusable prompt
Use this prompt as a starting brief, not a substitute for source material. Replace the brackets with approved information and remove instructions that do not apply. State the result you need before listing background details. If the assistant needs a missing fact to proceed, allow a focused question rather than demanding a complete answer that would require guessing.
Debug [minimal code] in [runtime]. Expected behavior is [expected]; actual behavior is [actual]. Explain the cause, propose a focused patch, and give success and failure tests. Do not rewrite unrelated functions.After the first response, describe the specific mismatch you want corrected. Name the omitted requirement, unsupported statement, or failing case instead of requesting a vaguely better version. Preserve the source facts during revision. Keep your accepted example together with the prompt so you can distinguish a useful recurring process from a one-time answer that happened to work.
Review checklist
- The original failing case now behaves correctly.
- Failure is not reported as success.
- No unrelated functionality was removed.
Review in two passes. First check substance: whether the output answers the intended question, preserves important constraints, and contains only supported commitments. Then check presentation: whether its structure, wording, and navigation make it usable for the intended reader. Fixing presentation first can make an incorrect answer more persuasive without making it more reliable.
Choose the review depth according to the consequence of being wrong. A fictional practice example may need a quick comparison; a public statement or external action needs stronger evidence. When the result depends on a source, open that source. When it depends on a calculation or program behavior, perform the relevant check. Record what you actually verified and keep unresolved points visibly separate.
| Stage | Useful record | Decision before moving on |
|---|---|---|
| Input | Approved source or reproducible sample | Is the task clear and the information permitted? |
| Draft | Output and explicitly stated assumptions | Does it match the requirement without invented facts? |
| Review | Checked claims or observed test results | Are important errors resolved and limits visible? |
| Handoff | Accepted result and unresolved questions | Can another person use it without hidden chat context? |
Practice exercise
Simulate the contact form’s success and failure paths with fictional requests. Write expected messages first, then run the proposed patch. Add an invalid email and inspect whether validation still occurs. Confirm that a failure never becomes a success notification. Save the reproduction and changed lines for review.
Common problems and repairs
If the error persists, compare actual logs with the hypothesis. If the patch touches unrelated functions, ask for a narrower change. If a test merely mirrors the implementation, replace it with a behavioral case. Do not hide failure by suppressing errors; make the user-facing state accurate.
Maintain a useful working process
Keep the reviewed result in the place where the work will continue, with a source or version reference when relevant. A teammate should be able to understand the purpose, confirmed information, and remaining questions without reading every chat turn. Remove temporary client details from reusable templates. Record the owner responsible for the next step so an attractive draft does not become an abandoned task.
Recheck the process when the task, source, or product changes. Start with the saved example most likely to be affected and compare the new result with the accepted baseline. If the same defect repeats, repair the instruction or review stage instead of patching the final wording each time. Keep the useful structure, but retire obsolete assumptions. This makes the workflow maintainable without turning every update into a complete rebuild.
Download the prompt and review checklist to keep your own practice record.
Frequently asked questions
How much code should I paste?
Provide the smallest example that reproduces the behavior plus relevant runtime information. Add neighboring code only when it changes the diagnosis.
Is compiling enough verification?
No. Run the failing scenario and meaningful success and failure cases. Code can compile while still choosing the wrong response or changing surrounding behavior.
What if the proposed fix is a rewrite?
Ask for a smaller patch tied to the identified cause. Understand why each changed line is necessary before accepting a broad replacement.
Should I include secrets for reproduction?
Use placeholders and sanitized fixtures. Credentials usually are not needed to explain control flow, validation, or error handling.
What should I save after the fix?
Keep the reproduction, patch rationale, and relevant checks. This evidence helps future reviewers understand the problem without reading the original chat.
Do I need every advanced feature to use this workflow?
No. Begin with the smallest version that produces the reviewed outcome. Check the specific controls and account requirements in the linked official help. If a feature is unavailable, use a sanitized manual input where appropriate instead of assuming an integration or mode exists.
How should I adapt the reusable prompt to my own work?
Replace the example with approved facts and specify the intended reader, result, and constraints. Remove irrelevant instructions rather than stacking more requirements indiscriminately. Keep uncertain details marked unknown, and compare the first output with the original brief before turning the prompt into a recurring process.
What information should I avoid putting into practice examples?
Use fictional or sanitized examples unless the real information is necessary and permitted for the product and account you use. Consider indirect identifiers and confidential context as well as obvious names or credentials. Preserve enough task structure to test the workflow without including unnecessary private detail.
How can I tell whether the assistant actually improved my work?
Compare the reviewed result with a baseline you understand. Look for fewer factual errors, clearer next actions, or reduced repair effort, depending on the task. Do not judge success solely by output length, polished formatting, or a confident tone. Record the defect corrected and the evidence supporting the improvement.
When should I review this guide’s product details again?
The product checks on this page are dated 4 October 2026. Consult the linked official documentation when account options, model names, permissions, or interfaces differ. The worked examples are editorial methods rather than a promise that every feature is available to every user or remains unchanged indefinitely.
Sources and related guides
Use these official resources to check product behavior and availability. The practical scenarios above are fictional examples, not measured product benchmarks. When a current interface differs from this guide, prefer the applicable official documentation and recheck your account. Keep source evidence beside conclusions rather than treating links as decorative proof.
Continue with Gemini API with AI Studio: Build a Small Tested App, or Gemini for Project Managers: Create Reviewable Plans. Compare another assistant’s approach in the practical Claude beginner guide.
