bug-intake

Scan Slack channels to triage bug reports, auto-fix small issues, and create GitHub issues.

8|1|Updated Aug 5, 2025
One-click install
npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill bug-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-intake
Source: https://github.com/ArtyMcLabin/ClaudeCode-global-config/tree/main/skills/bug-intake
Command: npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill bug-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates Slack bug intake across multiple workspaces by scanning bug-report channels, auto-fixing small bugs, and deferring larger work to the appropriate GitHub repository, while using emoji reactions to track state.

Core Features & Use Cases

  • Automated triage: identifies unprocessed bug reports in Slack channels and marks them with an intake lock for processing.
  • Auto-fix small bugs: applies quick, local fixes when possible and communicates results back to the reporter.
  • Big-work routing: creates GitHub issues in the correct repository, routing by workspace config and optional keyword-based routing.
  • Workspace-config aware: supports per-repo overrides and base/global flow combined via inheritance, enabling local customization.

Quick Start

Trigger a scan for bug reports in the configured Slack workspaces to begin triage. This requires a local config at .claude/skills/bug-intake/SKILL.md and access to Slack and GitHub to auto-fix small bugs or create issues for larger work.

Frequently Asked Questions about bug-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Slack bug intake and triage across multiple workspaces?

Slack bug intake automation scans configured channels to triage reports, auto-fix small issues, and defer larger work to GitHub issues. It uses emoji reactions to track processing state and supports per-repo overrides across multiple workspaces.

How does Slack bug triage route issues to the correct GitHub repository?

Bug triage routing uses workspace config resolution combined with optional keyword-based routing. This ensures bug reports are mapped to the correct GitHub repository based on workspace configuration and specific keywords in the report.

Can I customize bug report processing rules for different repositories?

Yes, workspace-config awareness supports per-repo overrides combined with base global flow via inheritance. This enables local customization of bug intake processing rules for different repositories within the same workspace.

Does automated bug triage require separate tokens for Slack and GitHub access?

Bug triage requires access to Slack and GitHub to auto-fix small bugs or create issues. The automation implements token mapping via the Slack skill and deployment policies to ensure reliable, auditable access across workspaces.

What happens when automated triage encounters a bug it cannot auto-fix?

When auto-fixing is not possible, the triage system defers larger work by creating a GitHub issue in the appropriate repository. The original bug report in Slack is tracked using emoji reactions to indicate its processing state.

What are the limitations of using emoji reactions for bug intake state tracking?

Emoji reactions track processing state but require consistent workspace configuration to avoid conflicts. The intake lock mechanism prevents duplicate processing, though complex multi-workspace setups need careful token mapping and config resolution to maintain reliability.