Bug report from a support ticket
OfficialOfficial · updated Nov 4, 2026 · v1.0.0
Turns a customer complaint into an engineering-ready bug report: steps to reproduce, expected vs actual, environment, impact, evidence, and questions to ask.
Sign up free to add this skill to your pod
You come back here after you sign in, and add it with one click.
When to use it
- A ticket reports something broken and needs to go to engineering
- Engineering bounced a ticket back for more detail
What you give it
- The ticket or chat thread
- Customer environment if known
- Your own reproduction attempt (optional)
What you get
A bug report ready to paste into Jira, Linear, or GitHub, plus questions for the customer.
Changelog
- v1.0.0 · Nov 4, 2026 · First release.
Sources
- Bug Writing Guidelines (2026-11-04)
- Bug Report Guidelines | WebKit (2026-11-04)
- Configuring issue templates for your repository (2026-11-04)
Related skills
- Support ticket triage Triages incoming tickets into a table with category, S1 to S4 severity, routing, and a first reply for each, sorted by what to answer first.
- Customer reply in our tone Drafts a support reply in your team's tone: answers the question first, owns mistakes, drops jargon, and ends with one clear next step.
- Spec review before build Reviews a PRD or spec before build for ambiguity, missing empty/loading/error/permission states, metrics, rollout, and a first-time user walk-through.