What problem does it solve? User-reported defects often get lost in chat or get filed as issues full of file paths and function names that go stale after a refactor. This Skill turns a conversational bug report into a well-structured GitHub issue that stays readable and actionable for maintainers over time. ## Core Features & Use Cases - Domain-language issue writing: Explores the codebase in parallel to absorb the project's own vocabulary, then writes issues that read like a maintainer wrote them, with no file paths, line numbers, or function names. - Duplicate detection and breakdown logic: Searches existing issues with gh issue list before filing, and splits multi-failure reports into ordered child issues with honest dependency links. - Structured templates: Enforces reproduction steps, expected vs. actual behavior, and a thirty-second read target on every issue filed via gh issue create. - Use Case: A user says "the import silently drops rows when the CSV has a trailing blank line — log this as a bug." The Skill clarifies minimally, checks for duplicates, and files a scoped issue with reproduction steps, returning the URL. ## Quick Start Report a bug in plain language and ask the assistant to file it as a GitHub issue, for example by saying "capture this: the export button does nothing on the second click."
