bug-report-format

What problem does it solve?

This skill eliminates ambiguous or incomplete bug reports by providing a strict, repeatable structure so engineers, QA, support, and operations can triage and act on issues—especially those affecting checkout, payment, order-state, preview approval, and fulfillment—without back-and-forth clarification.

Core Features & Use Cases

• Consistent Triage Structure: Defines a required order (Title, Severity, Summary, Environment, Preconditions, Steps, Expected vs Actual, Impact, Evidence, Suspected Area, Workaround, Open Questions) so each report contains the essential information.
• Business-Focused Impact: Emphasizes describing customer, revenue, and operational consequences to prioritize fixes correctly.
• Reproducibility & Evidence: Guides authors to include precise preconditions, atomic reproduction steps, identifiers, logs, and screenshots to enable immediate investigation.
• Use Case: Support or QA encountering a checkout that returns success but no order is created can produce a report that immediately points developers to the payment orchestration and order-state transition for triage.

Quick Start

Create a bug report for a checkout failure that does not create an order including title, severity, environment, preconditions, numbered reproduction steps, expected vs actual results, impact, evidence, suspected area, workaround, and open questions.