What problem does it solve?
This Skill converts informal bug descriptions into a structured, reproducible issue report that teams can triage and act on, while preventing premature root-cause speculation. It ensures the report contains clear reproduction steps, environment context, severity assessment, and a decision about whether a quick-fix path is appropriate.
Core Features & Use Cases
- Guided five-question intake that elicits precise phenomenon, reproduction steps, expected vs actual behavior, environment, and severity.
- Quick-channel detection by briefly inspecting referenced code to decide whether to recommend a fast fix or a full analysis path.
- YAML-frontmattered report template output (issue-report) and an exit checklist that ensures the report is review-ready before advancing to analysis or fix stages.
- Use case: a developer reports an intermittent UI crash; the Skill captures minimal reproducible steps, logs environment details, recommends severity, and either routes to fast fix or creates a standard issue folder.
Quick Start
Tell the assistant to record a bug by describing the observed phenomenon, step-by-step reproduction, environment details, and your severity assessment.