report-bug

What problem does it solve? Capturing a bug on the project tracker usually means stopping your work, remembering repro details, and writing a well-formed issue by hand. This Skill runs a short structured interview, mines the current conversation for error messages and context, and files a complete type:bug issue via the GitHub CLI without leaving the terminal. ## Core Features & Use Cases - Guided bug interview: Asks one numbered question at a time to fill every field of the issue template, including severity branches and reproduction steps. - Conversation seeding: When invoked with no argument, scans recent conversation context for stack traces, failing commands, and file paths to pre-fill the symptom. - Disciplined filing: Creates the issue with gh issue create using exactly the type:bug and needs-triage labels, sanitizes secrets from the body, and hands off to /triage for prioritization. - Use Case: You hit a crash mid-session and say "this is broken — file it". The Skill extracts the error from the conversation, asks a few clarifying questions, and opens a labeled issue with a clean title and full repro context. ## Quick Start Ask the assistant to report a bug describing the symptom you observed, then answer the follow-up questions and confirm to file the issue.