github-issue-creator

Create GitHub issues for MCPSpy with conventional titles and body files.

515|79|Updated Jul 17, 2025

Search Tags:#automation #github #issues #gh #conventional-commits #issue-creation

Ready to run

npx skills add https://github.com/alex-ilgayev/MCPSpy --skill github-issue-creator-alex-ilgayev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of well-structured GitHub issues for MCPSpy using the gh CLI, enabling consistent issue naming and detailed descriptions.

Core Features & Use Cases

Conventional issue titles: Use prefixes like feat(component):, fix(component):, or chore:.
Body templates & long content: Write long descriptions using a body file with gh issue create --body-file.
Issue content guidelines: Provide high-level design notes and actionable scope.

Quick Start

Ask to create a new issue with a concise title and description; the skill will invoke gh issue create and optionally use a body file for long content.

Frequently Asked Questions about github-issue-creator

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

FAQPage Schema

How do I automate GitHub issue creation with conventional commit formatting?▼

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.

Can I use gh CLI to create GitHub issues with long body content?▼

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.

What's the best way to standardize GitHub issue titles and structure across a team?▼

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.

How do I create GitHub issues with component tags and design notes?▼

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.

Do I need to manually write issue bodies when using gh CLI?▼

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.

Can this work for bug reports and feature requests in the same workflow?▼

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.