Skip to main content

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.

Zur Installation springen

Quellinformationen

Repository
tomevault-io/skills-registry
Letzte Quellaktivität
28. April 2026 um 22:53
Erkannte Sprache von SKILL.md
Englisch
Sterne
1
Forks
0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
2 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
github-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.
metadata
{"author":"alex-ilgayev"}
# 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 --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/alex-ilgayev) — claim your Tome and manage your conversions. <!-- tomevault:4.0:skill_md:2026-04-11 -->
Auf GitHub ansehen