Paste a tester's report into this prompt, fill the brackets, and send it to your coding assistant. One report per prompt. The template works with any assistant because it only describes the problem, the limits and the check.
The template
I have a bug in my app, reported by a tester. Please help me fix it.
CONTEXT
App: [one sentence: what the app does]
Screen / feature: [where the bug happens]
Platform: [Android / iOS / both]
REPORT
Steps:
1. [step]
2. [step]
3. [step]
Expected: [what should happen]
Actual: [what happens instead]
Device and OS: [e.g. model, OS version]
Extra (error text, screenshot description, logs): [paste or write "none"]
BEFORE YOU CHANGE ANYTHING
- Tell me in 2-3 sentences which part of the code you think causes this and why.
- If you are unsure, say so and list what you would need to see.
CONSTRAINTS
- Change only what is needed for this bug. Do not refactor or rename unrelated code.
- Do not add new libraries unless you explain why first.
- List every file you change and what changed in each.
REGRESSION CHECK
- This must keep working: [one nearby behaviour]
- Give me a short manual test I can run on a phone: exact steps and the expected result, for the bug and for the line above.
Filled example
This is an example, not a real report.
I have a bug in my app, reported by a tester. Please help me fix it.
CONTEXT
App: A shopping list app where you can share a list with family.
Screen / feature: Adding an item on the list screen
Platform: Android
REPORT
Steps:
1. Open an existing list
2. Tap "Add item" and type "milk"
3. Close the keyboard with the back button
Expected: "milk" appears in the list
Actual: The item is not saved and the field is empty again
Device and OS: Example phone, Android 14
Extra: no error message shown
BEFORE YOU CHANGE ANYTHING
- Tell me in 2-3 sentences which part of the code you think causes this and why.
- If you are unsure, say so and list what you would need to see.
CONSTRAINTS
- Change only what is needed for this bug. ...
REGRESSION CHECK
- This must keep working: adding an item with the keyboard's "Done" key
- Give me a short manual test ...
Adapting it
- Cannot reproduce? Replace "Steps" with what the tester wrote and add: "I could not reproduce this. Suggest what to log so I can capture it."
- Crash with a stack trace? Paste the trace under "Extra" and keep it short; the first lines usually matter most.
- UI problem? Describe the screen size and layout instead of code terms, and say what you see versus what you want.
- Several reports? Do not merge them. Run the template once per report, in order of impact.
After the answer
Read the list of changed files, run the manual test on a real phone, and then run the "must keep working" line. If it fails, go back with what you observed. For the full routine see the feedback loop with your coding assistant.
Need a good report to start with? Use the bug report template for testers.
Related: Vibe coding hub, real-device testing, how to test an app before launch.
AppReviewX gives you private, structured feedback from other developers (one feedback you write earns one credit; new accounts start with 0). Start free.