What problem does it solve? Incoming bug reports in Slack threads are noisy, duplicated, and often routed to the wrong owner, leading to duplicate tracker tickets and missed regressions. This Skill enforces a disciplined triage pipeline that classifies each report once, dedupes against the issue tracker, and creates tickets only when evidence gates pass. ## Core Features & Use Cases - Single thread-only verdict: Posts exactly one classified reply (bug, performance, feature request, question, or reroute) in the source Slack thread with a strict marker contract. - Cause-aware routing and dedupe: Traces the likely code path before assigning an owner, then searches the tracker by error signature, symptom, and source permalink to avoid duplicate tickets. - Fail-closed ticket creation: Creates a self-contained tracker issue only when all evidence, preflight, and dedupe gates pass, with compensation (cancel/close) if the verdict post fails. - Use Case: A user reports a crash in your Slack feedback channel. The automation reads the thread and attachments, checks recent commits for a regression, finds no existing ticket, files a linked issue in the tracker, and posts one verdict reply with the ticket link. ## Quick Start Invoke this Skill from the configured Benny triage automation with a Slack thread payload and tracker configuration to classify the report and post one verdict.
