| name | bug-report-writer |
| description | Transform informal bug descriptions into structured, professional bug reports. Use when the user describes a bug and needs it documented or filed. |
Bug Report Writer
Transform informal bug descriptions into professional, actionable bug reports.
Description
This skill takes informal bug descriptions, screenshots, logs, or verbal descriptions and produces well-structured bug reports following industry best practices. Reports are formatted for Jira, GitHub Issues, or any standard bug tracking system.
Instructions
When the user describes a bug or provides evidence of an issue:
- Extract Information: Identify the core issue, affected component, and observable behavior
- Determine Severity: Classify based on impact:
- Blocker: System unusable, no workaround
- Critical: Major feature broken, workaround exists
- Major: Feature partially broken, non-critical path
- Minor: Cosmetic or low-impact issue
- Trivial: Typo, alignment, minor polish
- Structure the Report: Create a complete bug report
- Add Context: Include environment details, frequency, and related areas
- Suggest Investigation Areas: Point developers to likely root cause areas
Output Template
## Bug Report
**Title**: [ACTION] [COMPONENT] - [Brief Description]
**Severity**: [Blocker/Critical/Major/Minor/Trivial]
**Priority**: [P0/P1/P2/P3]
**Component**: [affected module/feature]
**Environment**: [OS, Browser, App Version, API Version]
**Reported By**: [name]
**Date**: [date]
### Description
[Clear, concise description of the issue]
### Steps to Reproduce
1. [Precise step]
2. [Precise step]
3. [Precise step]
### Expected Behavior
[What should happen]
### Actual Behavior
[What actually happens]
### Frequency
[Always / Intermittent (X out of Y attempts) / One-time]
### Impact
[Who is affected and how — users, revenue, data integrity]
### Workaround
[Temporary solution if available, or "None"]
### Evidence
- Screenshots: [attached]
- Logs: [relevant log snippets]
- Console errors: [if applicable]
- Network requests: [if applicable]
### Additional Context
- First observed: [date/version]
- Related issues: [links]
- Possible root cause: [if identified]
### Labels
[regression, ui, api, data, security, performance]
Smart Defaults
- If the user doesn't specify severity, infer it from the description
- If environment is unknown, note it as "To be confirmed"
- Always suggest at least one possible investigation area for developers
- If screenshots are provided, reference specific visual elements
Example Usage
Write a bug report: The checkout button doesn't work on mobile when the cart has more than 10 items. I'm using Chrome on Android.
Here's a screenshot of the error. The page crashes after I submit the form with a file larger than 5MB.
