github-issue-creator

Creates well-structured GitHub issues for the MCPSpy project using the gh CLI tool. Use when asked to create issues, report bugs, or document features. Follows conventional naming with feat/chore/fix prefixes and maintains appropriate detail levels.

⭐478stars🔀68forks📁View on GitHub🕐Updated Dec 7, 2025⬇️2downloads

When & Why to Use This Skill

The GitHub Issue Creator skill automates the generation of professionally structured GitHub issues using the gh CLI tool. It streamlines the development workflow by enforcing standardized naming conventions (feat, fix, chore) and ensuring high-quality documentation for bug reports, feature requests, and technical debt management, specifically optimized for the MCPSpy project environment.

Use Cases

  • 1. Automated Bug Reporting: Instantly transform identified bugs into well-formatted GitHub issues with appropriate 'fix(component):' prefixes and technical context.
  • 2. Feature Request Documentation: Streamline the creation of new feature proposals by generating structured high-level design notes and actionable scopes for developers.
  • 3. Technical Debt Tracking: Quickly document maintenance tasks and refactoring needs using the 'chore:' prefix to keep the project backlog organized and transparent.
  • 4. Project Planning & Task Delegation: Convert complex project discussions into discrete, actionable work items with clear titles and descriptive bodies to facilitate better team collaboration.
namegithub-issue-creator
description"Creates well-structured GitHub issues for the MCPSpy project using the gh CLI tool. Use when asked to create issues, report bugs, or document features. Follows conventional naming with feat/chore/fix prefixes and maintains appropriate detail levels."
- Bash(gh issue*)

GitHub Issue Creator Skill

Automates the creation of well-structured GitHub issues for the MCPSpy project.

Tools and Usage

Use the gh issue CLI tool to create GitHub issues. If the issue body is rather long, write it to a temporary markdown file and use the gh issue create --body-file <file> option.

Issue Naming Convention

  • Use standard prefixes: feat(component):, chore:, fix(component):
  • Component examples: library-manager, ebpf, mcp, http, output
  • Brackets are optional but recommended for clarity
  • Keep titles concise and descriptive

Examples

  • feat(library-manager): add support for container runtime detection
  • chore: update dependencies to latest versions
  • fix(ebpf): handle kernel version compatibility issues

Issue Content Guidelines

What to Include

  • High-level design notes - focus on the "what" and "why"
  • POC-level details - enough to get started, not exhaustive
  • Actionable scope - should be implementable by a developer familiar with the codebase

What NOT to Include

  • Detailed test plans
  • Exhaustive acceptance criteria
  • Deep technical specifications
  • Code examples (unless absolutely necessary for clarity)

When to Use This Skill

  • Creating new feature requests
  • Reporting bugs and issues
  • Documenting technical debt
  • Planning work items for the MCPSpy project