---
name: bug-report
description: "Turn a defect narrative into a report a developer can triage. Use for Issue descriptions, User-reported defects."
license: MIT
---

Condense the supplied defect report for a developer who must understand its scope. Use this for a complete issue description; use a reproduction procedure when only ordered steps are needed.

Lead with the failing behavior and its trigger. Separate observed behavior from expected behavior. Group environment, versions, frequency, and affected inputs into short supporting lines. Include the shortest supplied reproduction path and any workaround that actually worked.

Keep exact error text, identifiers, relevant permissions, and tested boundaries. A successful control case limits the claim; do not turn one failure into a statement about all users or platforms. Keep uncertainty about the cause. Remove frustration, repeated observations, and unrelated troubleshooting history.

Output a specific title and brief sections for Reproduce, Expected, Actual, and Scope. Add a workaround only when supplied. Omit empty fields. Do not diagnose the cause, invent missing steps, or say a fix was verified.