github-issue-creator

Convert bug notes into structured GitHub issue reports with markdown templates.

2.9k|323|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/microsoft/skills --skill github-issue-creator-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-creator
Source: https://github.com/microsoft/skills/tree/main/.github/skills/github-issue-creator
Command: npx skills add https://github.com/microsoft/skills --skill github-issue-creator-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert scattered bug notes into structured GitHub issue reports.

Core Features & Use Cases

  • Structured conversion: turn error logs, voice notes, screenshots, and informal bug descriptions into actionable GitHub issues using a consistent template.
  • Markdown templates: output standardized issue content that can be copied or saved as Markdown files for review and tracking.
  • Output organization: publish issues to the /issues/ directory with a predictable naming convention to support batch processing and audits.

Quick Start

Paste or attach your bug notes and the tool will generate a GitHub issue draft in the repository's /issues/ directory.

Frequently Asked Questions about github-issue-creator

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

FAQPage Schema
How do I convert error logs and informal bug notes into structured GitHub issues?

To convert error logs and informal bug notes into structured GitHub issues, paste or attach your raw notes. The tool processes them through a markdown template to produce standardized, actionable issue reports.

Can I generate markdown GitHub issues from voice notes and screenshots?

Yes, you can generate markdown GitHub issues from voice notes and screenshots. The tool takes scattered, informal bug descriptions and converts them into a reproducible structure suitable for software project tracking.

Does this bug report converter save issues to a specific directory?

Yes, the bug report converter saves issues to a specific directory. It publishes the generated markdown issue drafts to the repository's /issues/ directory using a predictable file naming convention to support batch processing and audits.

What is the best way to automate GitHub issue creation from scattered bug reports?

The best way to automate GitHub issue creation from scattered bug reports is using a markdown-based template workflow. This ensures consistent file naming and a reproducible structure for every issue generated from your raw error logs.

Do I need a specific template format to turn bug descriptions into GitHub issues?

You do not need to provide a specific template format to turn bug descriptions into GitHub issues. The tool automatically fulfills a markdown-based template workflow, ensuring your output is consistently structured without manual formatting.