github-issue-creator

Automate GitHub issue creation using the gh CLI with conventional naming prefixes like feat(component):, fix(component):, or chore:. The Skill handles structured titles and long descriptions via temporary Markdown files, ensuring consistent issue formatting for projects following conventional commit standards.

Yes. The gh issue create command supports the --body-file flag to write lengthy descriptions to a temporary Markdown file, enabling detailed issue content without command-line length constraints. This Skill automates that workflow for structured, well-documented issues.

Standardize issue titles by adopting conventional naming with component tags—feat(library-manager):, fix(ebpf):, chore(mcp):—paired with detailed body templates. This Skill enforces that pattern via gh CLI automation, ensuring consistent naming and actionable scope across all team-created issues.

Use the gh issue create command with conventional prefixes and component tags (library-manager, ebpf, mcp, http, output). This Skill automates the process, optionally writing high-level design notes and scope details to a body file for comprehensive issue documentation.

No. The gh issue create --body-file approach lets you compose long descriptions in a temporary Markdown file, which this Skill handles automatically. This eliminates manual CLI escaping and enables rich formatting for complex issue content.

Yes. The Skill applies conventional prefixes (feat for features, fix for bugs, chore for maintenance) and component tags to both bug reports and feature requests, ensuring consistent structure and clarity regardless of issue type.