skills.rest
davidrrowley
davidrrowleyCOMMUNITY
Explore all skills by this author →
Website𝕏@davidrrowleyGitHub

github-issue-creator

Convert unstructured bug notes into structured GitHub-flavored markdown issue reports.

Updated Apr 12, 2026
Search Tags:#automation#markdown#screenshots#github#issue#triage#bug-report
One-click install
npx skills add https://github.com/davidrrowley/CortexYouV3 --skill github-issue-creator-davidrrowley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-creator
Source: https://github.com/davidrrowley/CortexYouV3/tree/main/.agents/skills/github-issue-creator
Command: npx skills add https://github.com/davidrrowley/CortexYouV3 --skill github-issue-creator-davidrrowley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns unstructured inputs like raw notes, error logs, voice dictation, and screenshots into clear, reproducible GitHub-flavored markdown issues so teams can triage and act quickly without hunting for missing details.

Core Features & Use Cases

  • Structured Issue Output: Generates a complete issue template with Summary, Environment, Reproduction Steps, Expected Behavior, Actual Behavior, Error Details, Visual Evidence, Impact, and Additional Context.
  • Multi-format Input Handling: Extracts facts from freeform voice dictation, pasted error messages, and image/GIF references and converts them into concise reproduction steps and formatted error blocks.
  • Safety & Hygiene: Redacts or replaces sensitive values with placeholders, classifies severity by impact, and enforces a filename convention for issues stored under issues/ at the repo root.
  • Use Case: Support engineers or QA reporters can paste a console dump or describe a failure out loud and receive a ready-to-file markdown issue that includes suggested severity and image references.

Quick Start

Ask the skill to convert the following notes and attachments into a GitHub issue and save it as a markdown file in the repository issues/ folder using the YYYY-MM-DD-short-description.md format.

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 unstructured bug notes and error logs into a formatted GitHub issue?▼

To convert unstructured bug notes into a GitHub issue, this Skill parses raw text, voice dictation, and screenshots to generate structured markdown files containing reproduction steps, environment details, and formatted error blocks.

Can I use voice dictation and screenshots to create a markdown bug report?▼

Yes, you can use voice dictation and screenshots to create a markdown bug report. This Skill extracts facts from multi-format inputs like audio transcriptions and image references, converting them into concise reproduction steps and inline visual evidence.

What is the best way to generate markdown issues with severity classification and redacted sensitive values?▼

The best way to generate markdown issues with severity classification and redacted sensitive values is using an automation Skill that classifies impact and replaces sensitive data with placeholders, producing structured bug reports ready for triage.

How do I format and save GitHub issues in a repository using a YYYY-MM-DD naming convention?▼

To format and save GitHub issues using a YYYY-MM-DD naming convention, this Skill produces markdown files in an issues/ directory at the repo root, naming them with the date and a short description for organized triage.

Does this bug report automation tool include specific sections like expected behavior and environment details?▼

Yes, this bug report automation tool includes specific sections like Summary, Environment, Reproduction Steps, Expected Behavior, Actual Behavior, Error Details, Visual Evidence, and Impact to ensure complete and actionable issue formatting.

What are the limitations when using markdown automation for triaging GitHub issues from messy inputs?▼

A limitation of using markdown automation for triaging GitHub issues is that it relies on the quality of unstructured inputs like raw notes and error logs, meaning highly ambiguous voice dictation or unclear screenshots may result in incomplete reproduction steps.

Related Skills

Explore More Software Engineering Skills→
bcascibcasci
3

draft-github-issues

Convert unstructured plans into structured GitHub issue YAML files.

Community
Intermediate
RemseyMailjardRemseyMailjard

github-issue-creator

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

Community
Intermediate
davpatel605-beepdavpatel605-beep

github-issues

Create, organize, and track GitHub issues via gh CLI or REST API.

Community
Intermediate
prismaprisma
47.5k

prisma-next-feedback

Route bug reports and feature requests to Prisma Next GitHub issues.

Official
Advanced