← ClaudeAtlas

bug-report-templatelisted

Use for any question or task about bug reports, including what makes a good one, turning an informal complaint or a CI failure (JUnit XML, Allure, pytest or Playwright output) into a report, and reports closed as cannot reproduce. Fills summary, environment, steps, expected vs actual and severity rationale, then checks each field is usable.
testland/qa · ★ 13 · Data & Documents · score 80
Install: claude install-skill testland/qa
# bug-report-template ## Overview A well-formed bug report is the input contract for triage, repro, and fix. Industry consensus from Mozilla's long-standing bug-writing guide ([mozilla-bug-writing][moz]) and the ISO/IEC/IEEE 29119-3:2021 incident-report format converges on the same eight fields: [moz]: https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html | Field | Purpose | |-------------------|--------------------------------------------------------------| | **Summary** | Triage line - describes the problem, not the cause. | | **Environment** | OS, build, browser/runtime version, locale, device. | | **Steps to Reproduce** | Numbered, deterministic, copy-pasteable. | | **Expected** | What should have happened. | | **Actual** | What did happen (verbatim error message if any). | | **Severity** | Impact on users (intrinsic to the bug). | | **Priority** | Order of fix relative to other bugs (extrinsic, business). | | **Reproducibility** | Always / Sometimes / Once / Unable. | > **Terminology note:** ISTQB distinguishes **error** (human action), > **defect / fault / bug** (imperfection in a work product), and > **failure** (deviation from delivered service). This skill uses > "bug" and "defect" interchangeably with "fault" reserved for the > code-level imperfectio