github-issue-creator · alex-ilgayev — Claude Code skill for GitHub issues
github-issue-creator is a Claude Code skill that creates GitHub issues for MCPSpy. It runs when asked to report a bug, propose a feature, or record technical debt.
Apache-2.0 1 installs ★ 525 updated 2026-01-16
npx skills add alex-ilgayev/MCPSpy --skill github-issue-creator -a claude-codeWhat github-issue-creator does
The skill creates MCPSpy issues with the gh issue command. For a longer description, it writes the text to a temporary Markdown file and passes it with --body-file.
Issue titles use feat, chore, or fix prefixes. The body focuses on the rationale, broad design, and actionable scope; it leaves out detailed test plans and exhaustive acceptance criteria. The gh CLI and GitHub access are required to create an issue.
What it helps with
- file a feature request for MCPSpy
- report a bug as a GitHub issue
- record technical debt for the project
- turn planned work into an actionable issue
Example prompts for the agent
- Create a GitHub issue for MCPSpy to add container runtime detection.
- Report a bug in MCPSpy: handle incompatible kernel versions.
- Write a GitHub issue documenting technical debt in MCPSpy.
How to install github-issue-creator
1Skills CLI (Vercel)
npx skills add alex-ilgayev/MCPSpy --skill github-issue-creator -a claude-code2Manually: put the files in place
~/.claude/skills/github-issue-creator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/github-issue-creator/
1Skills CLI (Vercel)
npx skills add alex-ilgayev/MCPSpy --skill github-issue-creator -a codex2Manually: put the files in place
.agents/skills/github-issue-creator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add alex-ilgayev/MCPSpy --skill github-issue-creator -a cursor2Manually: put the files in place
.cursor/skills/github-issue-creator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alex-ilgayev/MCPSpy .claude/skills/github-issue-creator2Manually: put the files in place
.github/skills/github-issue-creator/SKILL.md1Skills CLI (Vercel)
npx skills add alex-ilgayev/MCPSpy --skill github-issue-creator -a gemini-cli2Platform CLI
gemini skills install https://github.com/alex-ilgayev/MCPSpy --path .claude/skills/github-issue-creatorManually: put the files in place
.devin/skills/github-issue-creator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add alex-ilgayev/MCPSpy --skill github-issue-creator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about github-issue-creator
How do I install github-issue-creator in Claude Code?
Run npx skills add alex-ilgayev/MCPSpy --skill github-issue-creator -a claude-code. The skill is installed at ~/.claude/skills/github-issue-creator/SKILL.md.
What does github-issue-creator do?
It creates GitHub issues for MCPSpy with gh issue, using feat, chore, or fix prefixes and a concise, actionable description.
What does github-issue-creator need to work?
It requires the GitHub CLI, gh, and GitHub access to create issues for MCPSpy.
Source text
SKILL.md · Apache-2.0
--- 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." allowed-tools: - 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
© alex-ilgayev · Apache-2.0 · alex-ilgayev/MCPSpy
Similar skills
All skills for Git and GitHub →github-issue-creator by other authors comes first.