💬 Bug Report From a User Complaint
Turns a vague customer or user complaint about your app or website into a structured bug report with likely repro steps, missing details to ask for and a reply to the user.
The prompt
You are a QA lead turning a user's complaint into a bug report a developer can act on.
Product: {{product}}
What the user wrote:
{{complaint}}
What we know about their setup (may be partial): {{environment}}
Recent changes we shipped: {{recent_changes}}
Return, in Markdown:
1. **Bug title**: one line, specific, in the form "<what breaks> when <condition>".
2. **Summary**: two sentences in neutral language.
3. **Steps to reproduce (best guess)**: numbered, marked "assumed" where you are inferring from the complaint.
4. **Expected vs actual** behaviour.
5. **Environment**: list known fields and mark unknown ones as "ask user".
6. **Possible areas to look at**: up to 4, each tied to something in the complaint or the recent changes, labelled as hypotheses.
7. **Severity and priority suggestion** with a one-line reason (blocks payment, data loss, cosmetic, etc.).
8. **Questions for the user**: the 3-5 most useful questions, written plainly.
9. **Reply to the user**: under 100 words, thanks them, says what happens next and asks those questions. No promises about fix dates.
Rules: do not invent error messages, versions or logs that are not in the input. Keep hypotheses clearly separate from facts.
Variables
Replace each {{name}} before you send the prompt.
| Variable | What to put in | Example |
|---|---|---|
{{product}} | Your app or website. | A Shopify store with a custom size-chart popup and Stripe checkout |
{{complaint}} | Paste what the user said. | tried to buy the jacket 3 times on my phone and the pay button just spins forever. my card is fine, works everywhere else. also the size chart thing covers the whole screen and I cant close it. super annoying |
{{environment}} | Anything you know about their device, browser or account. | Order attempt logs show three abandoned checkouts from an iPhone; browser unknown |
{{recent_changes}} | What you changed recently. | Added the size-chart popup last Thursday; updated the checkout theme app extension on Monday |
Example
product: A Shopify store with a custom size-chart popup and Stripe checkout complaint: (complaint as in the example above) environment: Order attempt logs show three abandoned checkouts from an iPhone; browser unknown recent_changes: Added the size-chart popup last Thursday; updated the checkout theme app extension on Monday
### 1. Bug Title Payment submission hangs indefinitely and size-chart modal cannot be closed when checking out on an iPhone ### 2. Summary A customer reported that attempting to complete a jacket purchase on an iPhone resulted in an infinite loading spinner on the payment button across three attempts. Additionally, the size-chart popup occupies the entire viewport on their mobile device and provides no functional way to dismiss it. ### 3. Steps to Reproduce (Best Guess) 1. On an iPhone, navigate to the store and open a jacket product page. *(Assumed)* 2. Tap the option to view the size chart. *(Assumed)* 3. Attempt to close or dismiss the size-chart modal. *(Assumed)* 4. Add the jacket to the cart and proceed to checkout. *(Assumed)* 5. Fill in required customer and payment details. *(Assumed)* 6. Tap the pay button to complete the purchase. 7. Observe the pay button state and checkout progression. ### 4. Expected vs Actual Behaviour * **Expected:** * The size-chart popup displays properly scaled to the screen with an accessible close button to return to the previous view. * Tapping the pay button processes the card through Stripe and directs the customer to the order confirmation page. * **Actual:** * The size-chart popup covers the entire screen and cannot be closed. * Tapping the pay button causes it to enter an infinite spinning state, leaving the checkout incomplete and resulting in an abandoned checkout log. ### 5. Environment * **Device:** iPhone *(Known)* * **Operating System / iOS Version:** Unknown *(Ask user)* * **Browser:** Unknown (e.g., Safari, Chrome, in-app browser) *(Ask user)* * **Specific Product:** Jacket *(Item category known; exact product URL/SKU unknown — ask user)* * **Store Components:** Shopify checkout theme app extension…
Real, unedited output from a test run on Nov 2, 2026 · Gemini · model gemini-flash-latest.
Full output · Gemini (gemini-flash-latest)
### 1. Bug Title Payment submission hangs indefinitely and size-chart modal cannot be closed when checking out on an iPhone ### 2. Summary A customer reported that attempting to complete a jacket purchase on an iPhone resulted in an infinite loading spinner on the payment button across three attempts. Additionally, the size-chart popup occupies the entire viewport on their mobile device and provides no functional way to dismiss it. ### 3. Steps to Reproduce (Best Guess) 1. On an iPhone, navigate to the store and open a jacket product page. *(Assumed)* 2. Tap the option to view the size chart. *(Assumed)* 3. Attempt to close or dismiss the size-chart modal. *(Assumed)* 4. Add the jacket to the cart and proceed to checkout. *(Assumed)* 5. Fill in required customer and payment details. *(Assumed)* 6. Tap the pay button to complete the purchase. 7. Observe the pay button state and checkout progression. ### 4. Expected vs Actual Behaviour * **Expected:** * The size-chart popup displays properly scaled to the screen with an accessible close button to return to the previous view. * Tapping the pay button processes the card through Stripe and directs the customer to the order confirmation page. * **Actual:** * The size-chart popup covers the entire screen and cannot be closed. * Tapping the pay button causes it to enter an infinite spinning state, leaving the checkout incomplete and resulting in an abandoned checkout log. ### 5. Environment * **Device:** iPhone *(Known)* * **Operating System / iOS Version:** Unknown *(Ask user)* * **Browser:** Unknown (e.g., Safari, Chrome, in-app browser) *(Ask user)* * **Specific Product:** Jacket *(Item category known; exact product URL/SKU unknown — ask user)* * **Store Components:** Shopify checkout theme app extension (updated Monday), custom size-chart popup (added last Thursday), Stripe checkout *(Known)* ### 6. Possible Areas to Look At * **Hypothesis 1 (Checkout Extension / Payment):** The checkout theme app extension update deployed on Monday may contain a script error or unhandled asynchronous promise in the Stripe payment handler that prevents the submit action from resolving on WebKit/iOS. * **Hypothesis 2 (Size-Chart Layout):** The size-chart popup deployed last Thursday may lack responsive CSS constraints for mobile viewports, pushing the modal close button off-screen or behind other UI layers (`z-index` issue) on iOS. * **Hypothesis 3 (Script Conflict):** The custom size-chart popup script may be throwing an unhandled exception or capturing touch/click events globally, which could interfere with subsequent checkout interactions. ### 7. Severity and Priority Suggestion * **Severity:** Critical * **Priority:** P1 / High * **Reason:** Directly blocks revenue by preventing mobile users from completing payment. ### 8. Questions for the User 1. Which browser were you using on your iPhone (for example, Safari, Chrome, or a link opened inside Instagram/Facebook)? 2. Which specific jacket were you attempting to buy? 3. Did the size chart open while you were on the product page, or during the checkout steps? 4. Did you notice any error message on the screen before the pay button started spinning? --- ### 9. Reply to the User Hi there, Thank you for reaching out and letting us know about this. I'm sorry for the frustrating experience with the size chart and the payment button. Our engineering team is actively investigating what happened. To help us replicate and resolve this as quickly as possible, could you share: 1. Which browser you used on your iPhone (e.g., Safari, Chrome)? 2. Which jacket you were trying to purchase? 3. Where the size chart popped up (on the product page or during checkout)? We will follow up as soon as we have an update.
Full output · DeepSeek (deepseek-flash)
**Bug title** Pay button spins indefinitely and size-chart popup cannot be closed when attempting jacket checkout on iPhone **Summary** A user reports trying to buy a jacket three times on an iPhone, with the Pay button spinning indefinitely each time; order logs show three abandoned checkouts from an iPhone. The user also reports that the size-chart popup covers the full screen and cannot be closed. **Steps to reproduce (best guess)** 1. On an iPhone, open the jacket product page (exact product URL/SKU: ask user). [assumed] 2. Open the size-chart popup. [assumed] 3. Try to close the popup by tapping the close control, backdrop, or browser back. [assumed] 4. Add the jacket to the cart and continue to checkout. [assumed] 5. Enter payment details and tap Pay. [assumed] 6. Observe whether the Pay button spins indefinitely and whether an order is completed. [assumed] **Expected vs actual behaviour** | | Behaviour | |---|---| | **Expected** | The size-chart popup should be dismissible and should not block the page. The Pay button should complete checkout or show a clear error/retry state rather than spinning indefinitely. | | **Actual** | The size-chart popup covers the full screen and cannot be closed. The Pay button spins forever, and three abandoned checkouts from an iPhone are recorded. No error message was provided. | **Environment** - Product/store: Shopify store with custom size-chart popup and Stripe checkout — known - Device: iPhone — known from user report and order logs - iPhone model: ask user - iOS version: ask user - Browser: ask user; browser is unknown - Browser context: Safari, Chrome, or in-app browser — ask user - Product: jacket — exact name/URL/SKU: ask user - Order attempts: three abandoned checkouts from an iPhone — known from logs - Payment: Stripe checkout; user says card works elsewhere — known from report - Recent changes: size-chart popup shipped last Thursday; checkout theme app extension updated Monday — known - Error messages/console/network logs: none provided — ask user if any visible - Exact abandoned checkout IDs/timestamps: ask user or check logs **Possible areas to look at** - **Hypothesis:** The size-chart popup added last Thursday may have a missing/broken close handler or full-screen overlay CSS on mobile, causing it to trap the user. - **Hypothesis:** The Monday checkout theme app extension update may have introduced a mobile-specific script or overlay issue that prevents the Pay button from resolving. - **Hypothesis:** A conflict between the size-chart popup and checkout/theme scripts could be intercepting taps or leaving the page in a blocked state on iPhone. - **Hypothesis:** The Stripe checkout flow may be failing silently on mobile without returning an error to the user; check network/console behavior during payment. **Severity and priority suggestion** High severity / High priority — blocks payment for affected iPhone users and has already produced three abandoned checkouts. **Questions for the user** 1. What iPhone model and iOS version are you using? 2. Which browser were you using: Safari, Chrome, or an in-app browser? 3. Can you share the jacket product link or name? 4. Did the size-chart popup appear on the product page or during checkout, and did anything close it? 5. When you tapped Pay, did you see any error message, or did it only spin? Did your card or bank show any pending charge? **Reply to the user** Thanks for reporting this, and sorry the Pay button kept spinning while the size chart blocked your screen. We’re sending the details to the checkout and storefront team to investigate the iPhone checkout and popup behavior. To help us reproduce it, could you tell us your iPhone model and iOS version, which browser you used (Safari, Chrome, or an in-app browser), the jacket link or name, where the size chart appeared and whether anything closed it, and whether you saw an error or pending charge?
How to use it
Works in ChatGPT, Claude, Gemini and DeepSeek, and pairs well with Cursor or Claude Code when you hand the report straight to your coding agent. Paste the complaint as the user wrote it and get a clean bug report plus a friendly reply asking for the details you’re missing.
Guesses stay labelled as “assumed” or “hypothesis”, so a developer never chases an error message nobody actually saw.
Test log
| Date (UTC) | Tool | Model | Run | Result | Checks | Tokens in / out |
|---|---|---|---|---|---|---|
| Nov 2, 2026 | Gemini | gemini-flash-latest | Test | Passed | 3/3
| 376 / 853 |
| Nov 2, 2026 | DeepSeek | deepseek-flash | Test | Passed | 3/3
| 394 / 4,284 |
Each row is a real run recorded by our test runner. For each tool, the latest test run decides whether it appears under “Tested on”. Baseline runs do the same task with no skill installed and never count.