github-issue-creator

Converts messy notes and error logs into structured GitHub issue markdown files.

Updated Aug 23, 2026

Search Tags:#automation #markdown #github #issues #incident-management #bug-report

Ready to run

npx skills add https://github.com/rrbanda/skills --skill github-issue-creator-rrbanda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue-creator
Source: https://github.com/rrbanda/skills/tree/main/skills/devops/github-issue-creator
Command: npx skills add https://github.com/rrbanda/skills --skill github-issue-creator-rrbanda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts messy notes, error logs, or voice dictation into structured GitHub issues to accelerate triage and resolution.

Core Features & Use Cases

Automatic extraction and formatting of issue fields (Summary, Reproduction Steps, Expected Behavior, and Impact).
Preserves attachments and visual evidence for issues.
Outputs standardized markdown files to /issues/ with a consistent template to streamline triage.

Quick Start

Paste the raw bug report or notes and specify the target GitHub repository to generate a formatted issue.

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 messy notes and error logs into structured GitHub issues?▼

To convert messy notes into structured GitHub issues, paste your raw text or voice dictation into the tool and specify the target repository. It automatically extracts fields like Summary, Reproduction Steps, Expected Behavior, and Impact, then outputs a formatted markdown file.

Can I create GitHub issues from voice dictation for multiple repositories?▼

Yes, you can create GitHub issues from voice dictation across multiple repositories and projects. The tool processes the raw text input, preserves any attachments or visual evidence, and generates standardized markdown issue files for each specified target repository.

What is the best way to format bug reports and incident management notes for GitHub?▼

The best way to format bug reports and incident management notes is using a standardized markdown template. This tool processes raw notes or error logs, extracts reproduction steps and impact assessments, and outputs consistent markdown files to your /issues directory to streamline triage.

Does this issue generation tool preserve images and attachments from my raw notes?▼

Yes, the issue generation process preserves attachments and visual evidence from your raw notes. When it extracts issue fields and outputs the standardized markdown file to the /issues directory, any supporting images or attachments included in the original input are retained.

How do I generate standardized markdown files for bug reports to speed up triage?▼

You can generate standardized markdown files for bug reports by inputting raw notes and specifying a repository. The tool applies a consistent template that structures summaries, reproduction steps, and impact details, producing uniform markdown files in the /issues directory to accelerate triage.