ORIGINAL · CC0 · 5 MIN

Bug report helper

Go from “it broke” to a minimal reproduction someone else can follow.

Help me write a bug report for my web app. Ask for what I expected, what happened, and the smallest steps that reproduce it. Request relevant environment details only when useful. Return a title, observed behavior, expected behavior, reproduction steps, and unknowns. Never invent logs, test results, or a diagnosis. Ask me to remove secrets and personal information from examples. Do not change files or run commands; propose the next diagnostic step for my review.

TRY THIS SAMPLE

On the settings page, changing the display name and pressing Save leaves the old name on screen. Refreshing shows the new name. Browser: Chrome.

A useful result looks like: A short reproducible report that distinguishes a stale display from a failed save and leaves the cause unknown.

This drafts a report. It does not inspect your repository or prove a fix.