skills.rest
HellKaiser45
HellKaiser45COMMUNITY
Explore all skills by this author →
GitHub

github-issue-creator

Convert raw notes and error logs into structured GitHub Markdown issues.

Updated Feb 4, 2026
Search Tags:#automation#markdown#logs#github#notes#issue
One-click install
npx skills add https://github.com/HellKaiser45/Podlet --skill github-issue-creator-hellkaiser45
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-creator
Source: https://github.com/HellKaiser45/Podlet/tree/main/.podlet/skills/github-issue-creator
Command: npx skills add https://github.com/HellKaiser45/Podlet --skill github-issue-creator-hellkaiser45

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts raw notes, error logs, voice dictations, or screenshots into crisp GitHub-flavored Markdown issue reports, enabling faster triage and consistent documentation.

Core Features & Use Cases

  • Structured GitHub issues: Generate Markdown files that follow a standardized template with sections like Summary, Environment, Reproduction Steps, Expected Behavior, Actual Behavior, Error Details, Visual Evidence, and Impact.
  • Input flexibility: Accepts diverse inputs (notes, logs, dictations, screenshots) and extracts actionable information.
  • Evidence support: Attaches images/GIF references to captured evidence within the issue.
  • Output location: Creates Markdown files in the repo's /issues/ directory using the naming convention YYYY-MM-DD-short-description.md.

Quick Start

Provide a raw bug note or error log and the tool will generate a ready-to-file GitHub 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 raw notes and error logs into structured GitHub issues?▼

Yes, you can generate GitHub Markdown issue reports from voice dictations. The tool accepts diverse inputs including dictations, raw notes, and error logs, then extracts actionable information to produce consistent Markdown issues.

What is the best way to create standardized bug reports from messy QA notes?▼

GitHub issue reports generated from raw notes include structured sections like Summary, Environment, Reproduction Steps, Expected Behavior, Actual Behavior, Error Details, Visual Evidence, and Impact for fast triage.

Can I attach image evidence to a GitHub issue generated from error logs?▼

Generated GitHub issues are output as Markdown files in the repo's /issues/ directory using the naming convention YYYY-MM-DD-short-description.md for consistent documentation and easy access.

Does this issue generation tool work with feature requests and QA notes across different projects?▼

To automate GitHub issue creation from raw text, provide your unstructured bug note or error log directly to the tool. It will process the input and generate a ready-to-file Markdown issue file.

Related Skills

Explore More Software Engineering Skills→
RemseyMailjardRemseyMailjard

github-issue-creator

Convert messy bug notes and logs into structured GitHub issue markdown files.

Community
Intermediate
dalawwadalawwa

git:load-issues

Load open GitHub issues and save each as a markdown file.

Community
Intermediate
gittowergittower
413

gh-issue

Create GitHub issues with repository-specific formatting and labels.

Official
Intermediate
saitarrunsaitarrun
4

triage

Enforce structured issue triage workflows with defined roles and states.

Community
Intermediate