github-issue-creator

To convert raw error logs and screenshots into a structured GitHub issue, this Skill fills a predefined markdown template with summary, reproduction steps, expected vs actual outcomes, and visual evidence references. It safely infers missing context using placeholders to ensure clear triage.

The best way to format bug reporting notes for triage is applying a GitHub-flavored markdown template that includes severity classification, environment details, and impact justification. This standardizes regression reporting and turns messy inputs into structured documentation.

Yes, you can use voice dictation to create a markdown bug report for GitHub. The Skill processes raw voice inputs alongside error logs and screenshots, converting them directly into a structured issue template with appropriate context and reproduction steps.

Severity classification during GitHub issue generation converts described impact into Critical, High, Medium, or Low severity levels. It automatically generates a short justification within the markdown template based on the provided bug notes and failure context.

Generated GitHub issue markdown files are saved in the repository root issues directory. They are automatically named using the YYYY-MM-DD-short-description naming convention to maintain chronological order and easy retrieval for maintainers.