Slack-Ticket Overview

slack-ticket bridges the gap between your team’s Slack discussions and GitHub issue tracking. When bugs, feature requests, or support tickets surface in Slack, the CLI transforms fragmented conversations into perfectly structured, actionable GitHub issues—in seconds.

The Problem

Your team chats in Slack. Issues live in GitHub. The gap between these two worlds creates friction:

• Information loss: Important details discussed in threads get buried or forgotten
• Manual retyping: Someone has to manually copy-paste Slack messages into GitHub format
• Inconsistent formatting: Each team member creates issues differently, making them hard to search and triage
• Stale issues: New information in Slack never makes it back to existing GitHub issues

The Solution

slack-ticket uses AI to understand your Slack conversations and automatically generates well-structured GitHub issues:

• Thread analysis: Fetches Slack threads (configurable depth up to 10 messages)
• AI structuring: Converts informal chat into proper issue format with title, summary, steps to reproduce, expected vs actual behavior
• Smart labeling: Auto-applies severity, component, and keyword-based labels
• Project assignment: Automatically adds issues to your GitHub Projects
• Two-way sync: Append new Slack messages to existing issues as they evolve

Key Features

AI-Powered Issue Generation

The AI analyzes your Slack conversation and extracts the key information:

slack-ticket create https://yourworkspace.slack.com/archives/C12345/p123456789

The tool generates a GitHub issue with:

• Concise, descriptive title (max 80 characters)
• 1-3 sentence summary
• Steps to reproduce (when inferable)
• Expected vs actual behavior

Flexible Labeling System

slack-ticket applies labels based on multiple strategies:

Multi-Provider AI Support

Choose the AI provider that works for your team:

• OpenAI (GPT-4o, GPT-4o mini)
• Anthropic (Claude 3.5 Sonnet, Claude 3 Haiku)
• Google Gemini
• Ollama (local, self-hosted)

Konsent Integration

slack-ticket is designed to work seamlessly within the konsent project ecosystem. While konsent provides the architectural foundation and team coordination patterns, slack-ticket handles the tactical work of turning discussions into trackable work items.

Teams using konsent can leverage slack-ticket to:

1. Capture decisions: Transform architecture discussions into GitHub issues for implementation
2. Track action items: Convert sprint planning conversations into properly labeled tasks
3. Maintain context: Keep GitHub issues in sync with Slack discussions as projects evolve

Quick Start

# Install globally
npm install -g slack-ticket

# Run interactive setup
slack-ticket setup

# Create a GitHub issue from a Slack thread
slack-ticket create <slack-thread-url>

For detailed setup instructions, see the Setup Guide.

Why Teams Choose slack-ticket

1. Saves hours weekly: No more manual copy-pasting from Slack to GitHub
2. Consistent issue quality: Every issue follows the same structured format
3. Never lose context: New Slack messages automatically update existing issues
4. Works where you work: CLI integrates into existing workflows and scripts

Learn more about the CLI commands or AI analysis features.