Fix a broken Delete button in a GitHub repo
Community report: after giving Jules access to the GitHub repo, The builder picked the repo and branch and asked it to fix the broken Delete button. The requirements were to match the Delete button in another module and to disable deletion after two hours. Jules produced the code changes and the branch appeared in GitHub, and it wrote test cases that nobody asked for.
- Agent or tool
- Gemini
- Topic
- Software Development
- Reported on
- Blog
- Added
- 2026-10-15
Why it matters
Coding agents are moving from autocomplete to doing whole tasks: reading a codebase, making a plan and changing many files. This case is a concrete example of where that works in practice. It is one of 106 sightings filed under Software Development on Agent Sightings (number 100 by interest), and one of 14 involving Gemini.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Gemini or any similar agent and adjust the details to your situation.
In this repo, fix a broken Delete button in a GitHub repo. Read relevant code, apply a minimal patch, run available checks, and summarize the diff. Stop before merge or deploy.
The prompt breaks down into 3 steps you can check as the agent works:
- In this repo, fix a broken Delete button in a GitHub repo.
- Read relevant code, apply a minimal patch, run available checks, and summarize the diff.
- Stop before merge or deploy.
Tip: Work on a fresh branch, ask for a plan before edits, and review the diff and test results before merging.
Source
Read the original first-hand account on Blog: https://calvin.my/posts/fixing-a-bug-using-ai-with-google-jules. Our summary is a paraphrase; details are in the source.