⚡

How to Use the Shortcut

Convert Slack conversations into GitHub issues in seconds

📋 Before You Start

Make sure you have:

  • ✓ Completed GitHub setup: Connected your GitHub account and set a default repository
  • ✓ Repository access: Write permissions to create issues in your target repository
  • ✓ Available quota: Issues remaining in your current billing plan

🎯 What is the Message Shortcut?

The message shortcut is Issue Pilot's main feature that allows you to:

🤖

AI Summarization

Automatically summarize entire Slack threads using advanced AI technology

📝

Auto-Create Issues

Generate well-structured GitHub issues with title, description, and context

🔗

Preserve Context

Maintain all important details from the conversation in the issue

⚡

Save Time

Skip manual copying and pasting - create issues in seconds

1 Find the Conversation

Identify the Slack message or thread you want to convert into a GitHub issue:

💡 Best Practices:

  • • Bug reports: Select the initial message reporting the bug
  • • Feature requests: Choose the message where the feature is first discussed
  • • Discussions: Pick the first message in the thread for full context
  • • Thread context: Issue Pilot will automatically include all replies in the thread

2 Access the Shortcut Menu

There are two ways to access the Issue Pilot shortcut:

Option A Three-Dot Menu (Desktop)

  1. Hover your mouse over the message you want to convert
  2. Three small dots (⋮) will appear on the right side of the message
  3. Click the three-dot menu
  4. Look for "Create GitHub Issue" in the dropdown menu (under "More message shortcuts")
  5. Click "Create GitHub Issue"

Option B Right-Click Menu (Desktop)

  1. Right-click (or Control+Click on Mac) on the message
  2. A context menu will appear
  3. Scroll down to find "Create GitHub Issue"
  4. Click it

📱 Mobile Users: On Slack mobile apps, long-press on the message, then look for "Create GitHub Issue" in the menu that appears.

3 Choose Repository (Optional)

After clicking the shortcut, a modal window will appear:

Repository Slug Field:

owner/repo_name

This field is pre-filled with your default repository (if you've set one).

You have two options:

Option 1: Use Default Repository

  • • Leave the field as-is (it shows your default repo)
  • • Click "Create Issue" button
  • • ✅ Fastest option for regular workflow

Option 2: Specify Different Repository

  • • Clear the field and type a different repository
  • • Format: owner/repository-name
  • • Example: octocat/Hello-World
  • • Click "Create Issue" button
  • • ✅ Useful for multi-repo teams

⚠️ Important: You must have write access to the repository you specify. Otherwise, the issue creation will fail.

4 AI Processing & Issue Creation

Once you click "Create Issue", Issue Pilot springs into action:

1

Fetching Messages

Issue Pilot retrieves the entire thread, including all replies

2

AI Summarization

The AI analyzes the conversation and extracts key points

3

Generating Issue

AI creates a concise title and detailed description in Markdown format

4

Creating in GitHub

Issue is posted to your specified repository

ℹ️ Processing time: Usually takes 5-15 seconds depending on thread length and AI response time.

5 Confirmation & Next Steps

After successful issue creation:

  1. Success Message: Issue Pilot posts a message in the thread:

    @YourName Successfully created issue in `owner/repo`: https://github.com/owner/repo/issues/123

  2. Click the Link: The message includes a direct link to the newly created GitHub issue
  3. Review the Issue: Open the GitHub issue to review:
    • Title generated by AI
    • Description with summarized context
    • Key points extracted from the conversation
  4. Edit if Needed: You can edit the issue on GitHub to:
    • Refine the title
    • Add additional context
    • Add labels, assignees, or milestones
    • Link to related issues

🎉 Success! You've just converted a Slack conversation into a GitHub issue in seconds!

📦 What Gets Included in the Issue?

The AI analyzes the conversation and creates:

📌 Title (Under 100 characters)

A concise, descriptive title summarizing the main topic

Example: "Add dark mode toggle to user settings page"

📝 Body (Comprehensive Markdown)

A detailed description including:

  • • Main problem or request
  • • Key discussion points
  • • Important context from the thread
  • • Any decisions or action items mentioned
  • • Technical details or requirements

💡 Note: The AI writes in third person and doesn't mention specific Slack usernames to keep issues professional and focused on content.

📊 Understanding Usage Limits

Your plan determines how many issues you can create per month:

Free Plan

5

issues/month

Starter

50

issues/month

Intermediate

200

issues/month

Checking Your Usage:

  1. 1. Go to the billing portal
  2. 2. View the "Issues Created" card on the dashboard
  3. 3. See your current usage vs. monthly limit
  4. 4. Upgrade if you're approaching your limit

⚠️ Limit Reached: If you've used all your monthly issues, you'll see an error message. Upgrade your plan or wait until next month to create more issues.

💡 Pro Tips & Best Practices

📌 Use Descriptive Thread Titles

Start threads with clear context - the AI will use this to generate better issue titles

🎯 Convert at the Right Time

Wait until the discussion has enough context before creating the issue. You can always add more details in GitHub later.

📝 Keep Important Details in the Thread

Technical specs, reproduction steps, and screenshots in the thread will be included in the AI summary

✏️ Review and Edit on GitHub

Always review the generated issue and add any missing details, labels, or assignees on GitHub

🔄 Use for Different Use Cases

Great for: bug reports, feature requests, support tickets, documentation needs, and technical discussions

👥 Team Collaboration

Anyone in the workspace can create issues to their own GitHub repos - perfect for distributed teams

🔧 Troubleshooting Common Issues

Don't see "Create GitHub Issue" in the menu?

  • • Make sure Issue Pilot is installed in your workspace
  • • Verify you've completed the GitHub setup (/github-setup)
  • • Try refreshing your Slack client
  • • Check if you have permission to use shortcuts in this channel

Error: "Could not access repository"

  • • Verify the repository name format: owner/repo
  • • Ensure you have write access to the repository
  • • Check if the repository exists and is spelled correctly
  • • For organization repos, verify Issue Pilot has access to that org

Error: "GitHub not configured"

  • • Run /github-setup to connect your GitHub account
  • • Make sure you completed the authorization on GitHub
  • • Try disconnecting and reconnecting your GitHub account

Error: "Usage limit exceeded"

  • • You've used all issues for the month on your current plan
  • • Upgrade your plan for more issues
  • • Or wait until the start of next month when limits reset

Modal doesn't appear after clicking shortcut?

  • • Check your popup blocker settings
  • • Try using Slack in a different browser
  • • Update your Slack client to the latest version

Issue created but content seems incomplete?

  • The AI does its best but may miss some nuances
  • • Edit the issue on GitHub to add any missing details
  • • Long threads may be truncated - consider splitting into multiple issues

Still having problems?

Contact support at [email protected] with:

  • • Screenshot of the error message
  • • Repository name you're trying to use
  • • Your workspace and user details

🎯 You're Ready to Go!

Now you know how to use Issue Pilot's powerful shortcut feature. Here are some additional resources:

📊 Manage Your Plan

Track usage, upgrade your plan, or manage billing.

View Billing Guide →

⚙️ Configure Settings

Change your default repository or reconnect GitHub.

View Setup Guide →

Start Creating Issues Now! 🚀

Transform your Slack conversations into actionable GitHub issues in seconds

Need help? Email us at [email protected]