Prompt · Developer Tools

Bug Report Formatter

Turns a vague bug complaint into a crisp, reproducible bug report.

Have ready: Paste the complaint and any context you have

Fill in · 4 fields

PASTE THE COMPLAINT, USER WORDS, SUPPORT TICKET, OR YOUR OWN RUSHED NOTEcomponentsymptomcondition

Your prompt

Turn this complaint into a proper bug report. First extract, then interrogate, then write.

Raw complaint:
[PASTE THE COMPLAINT, USER WORDS, SUPPORT TICKET, OR YOUR OWN RUSHED NOTE]

Step 1: Extract what IS specified (environment hints, steps, expected vs actual).
Step 2: List the questions I must answer before this is actionable, environment, repro steps, frequency, scope (one user or all?), recent changes. Ask me only the questions that block reproduction.
Step 3: Once I answer, write the final report:

**Title:** [component]: [symptom] under [condition]
**Environment:** versions, OS/browser, account/tenant specifics
**Steps to reproduce:** numbered, starting from a clean state
**Expected / Actual:**
**Frequency & scope:**
**Logs/evidence:** what to attach
**Suspected area:** your best hypothesis (marked as hypothesis)

If the complaint is missing something critical, say what and why it blocks debugging, don't pad the report with guesses.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Rollout Planner

Test Pyramid Planner

Serialization Chooser

CLI UX Review

Query Plan Explainer

Dependency Upgrade Plan