← All templates
Engineering

Bug reports to github issues template

Dedupe, structure, and assign chat bug reports in GitHub.

Use this template →

Kollab reads @bot messages, fills in reproduction steps, priority, and owner, then sends the GitHub issue link back to chat.

How it works

  1. 01

    Report inside chat

    Users, support, or engineers mention the bot where the problem already appeared, without opening GitHub first.

  2. 02

    Structure and dedupe

    Kollab extracts reproduction details, impact, and module, then checks GitHub for similar issues.

  3. 03

    Create and assign

    For new reports, Kollab creates a consistent issue with labels, priority, and the right owner.

  4. 04

    Close the loop in chat

    The chat receives the issue link, assignee, and status so the report no longer lives only as a message.

Starter prompt

I want to turn bug reports from team chat into GitHub issues automatically.

Chat source: [Slack / Telegram / Discord / team chat]
Target repository: [owner/repo]
Default language: English

Whenever someone mentions the bot with a bug, crash, screenshot, error log, or feature request, follow this workflow:
1. Classify the message as a bug, feature request, support issue, or unclear report.
2. Extract the title, user impact, reproduction steps, actual behavior, expected behavior, screenshots, and log clues.
3. Search existing GitHub issues for likely duplicates. If there is a strong duplicate, reply with that issue link instead of creating a new one.
4. If it is new, create a structured GitHub issue with the right labels, priority, and module.
5. Assign the issue to the owner for that module: [frontend owner], [backend owner], [mobile owner].
6. Reply in the original chat with the GitHub issue link, assignee, reasoning, and next status.
Use this template →