Github Issue Creator
Productivitygithub-issue-creatorGithub Issue Creator is an Agent Skill for productivity published in the alex-ilgayev/MCPSpy repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/alex-ilgayev/MCPSpy/blob/HEAD/.claude/skills/github-issue-creator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/github-issue-creator, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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 detectionchore: update dependencies to latest versionsfix(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