1
Report in chat, naturally
No special format required. Anyone on the team messages the feedback channel the way they normally would.
Product & Engineering
Report a Bug in Slack. Find It Triaged in GitHub.
The entire issue creation and assignment pipeline, handled by an agent. This is how Kollab's own team works.
Every team has the same problem: bugs get reported in Slack, captured nowhere, and fall through the cracks. Someone always has to be the bridge between "hey this is broken" and a properly formatted GitHub issue assigned to the right developer.
Kollab's IM Bot eliminates that bottleneck. Your team reports naturally in Slack or Telegram. The agent classifies the issue, fills in the structure, creates the GitHub issue, and assigns it — then confirms back in chat. This is the exact setup Kollab's own product team runs internally.
Chat-to-GitHub flow visual
나중에 비주얼이나 스크린샷을 넣을 자리
Reserve for Slack / Telegram to GitHub flow illustration.
Issue creation screenshot
나중에 비주얼이나 스크린샷을 넣을 자리
Reserve for a real bot reply + GitHub issue pairing screenshot.
The prompt
이 prompt 를 아무 Kollab 대화에 붙여 넣으면 바로 시작할 수 있습니다.
I want to set up an automated pipeline: when someone reports a bug or feature request in our Slack channel #[channel-name], Kollab should handle the rest.
For every message in that channel:
1. Classify it as: Bug / Feature Request / Question / Unclear
2. For bugs — extract: reported behavior, expected behavior, and reproduction steps (if mentioned). If steps are missing, note that.
3. For feature requests — identify the user's underlying goal and write a one-line scope statement.
4. Create a GitHub issue in [org/repo] with:
- A clear, specific title (not just "it's broken")
- Structured body: Description / Steps to Reproduce / Expected vs Actual Behavior / Priority
- Label: "bug" or "enhancement"
- Assignment: [Frontend dev name] for UI/frontend issues, [Backend dev name] for API/data issues, leave unassigned if unclear
5. Reply in Slack with: issue type, GitHub link, and assigned developer name — so the reporter knows it was captured.
GitHub repo: [your-org/your-repo]
Slack channel: #[channel-name]이 workflow 에서 쓰는 Kollab 기능
IM BotMCP — GitHub ConnectorAgent SkillsMemory
How it works
2
Agent reads, classifies, and structures
Kollab's Bot reads the message, identifies whether it's a bug or feature request, and pulls out the relevant details — filling in what's there and noting what's missing.
3
GitHub issue created automatically
Full issue body with structured sections, correct labels, and smart assignment based on what part of the product the report touches.
4
Loop closed in chat
Bot replies with the GitHub link and assignee. The reporter knows it was captured. Nothing falls through the cracks.
What you get
In chat (from Kollab Bot):
Captured — GitHub issue #247 created
Type: Bug | Priority: High | Assigned: @alexdev (frontend)
→ github.com/yourorg/yourrepo/issues/247
On GitHub — Issue #247
Title: Dashboard fails to load when user has more than 500 projects
Labels: bug, frontend, P1
Assignee: alexdev
Description:
Users with large workspaces report the dashboard hanging on load.
Reported behavior: blank screen after login, no error shown.
Expected behavior: dashboard loads within 3 seconds.
Steps to reproduce: [not provided — flagged for follow-up]Stop being the bridge between chat and GitHub.
Set up the pipeline once. Every report gets captured, classified, and assigned.