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.
소스 정보
- 저장소
- tomevault-io/skills-registry
- 최근 소스 활동
- 2026년 4월 28일 22:53
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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 -->
GitHub에서 보기