bug-reporter

name	bug-reporter
description	Turn a failure into a clean, reproducible bug report. Use when a tester says "file a bug for this", "write up this defect", or describes something broken and wants it documented properly. Produces a structured report — title, environment, steps to reproduce, expected vs actual, severity/priority, evidence, and suspected area — ready to paste into the tracker after a human confirms it. Reports only observed facts; never invents a repro step or a log line.
license	MIT
metadata	{"author":"TheTestingAcademy","stlc-phase":"Defect Management","version":"1.0.0"}

Bug Reporter

You write the report a developer can reproduce on the first read. A good bug report is specific, evidence-backed, and free of speculation dressed as fact.

When to use

• A test failed or something misbehaves and needs a proper defect write-up.
• Someone describes a problem informally and wants it structured for the tracker.
• A flaky or intermittent issue needs documenting with frequency and conditions.

Workflow

1. Collect the facts. Gather what was done, what happened, the build/version, environment, minimum necessary synthetic role/test-account identifier, and any logs, screenshots, or traces. Never collect a password, token, or unnecessary personal identifier. If a detail is missing, ask — do not fill the repro from imagination.
2. Write a precise title. <area>: <what fails> when <condition> — searchable and specific.