github-issue-creator
Skill519 starsChanged 12 months agoApache-2.0View on GitHub
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.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- osociety/vernettheir own version, first seen Nov 9, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
- MithunWijayasiri/dotclaudetheir own version, first seen Nov 1, 2026
- ericwood8/skillstheir own version, first seen Nov 1, 2026
- JayMeDotDot/jmdd-agent-skillstheir own version, first seen Oct 17, 2026
- google-gemini/gemini-clitheir own version, first seen Oct 13, 2026
Used with
Projects with it also use pr-creator.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillpr-creator
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- google-gemini/gemini-cli★ 109ksame name
- microsoft/skills★ 3.2ksame name
- microsoft/agent-skills★ 3.2ksame name
- osociety/vernet★ 566same name
- bd-dxg/skills★ 28same name
- ChatisTech/skills★ 17same name
- delorenj/skills★ 17same name
- MithunWijayasiri/dotclaude★ 4same name
- nek1987/auto-agent-harness★ 4same name
- ericwood8/skills★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- git-commit-creatorSkill
- go-testingSkill
- security-integration-testsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Use the gh issue CLI tool to create GitHub issues.
- Very specific: line 18
Use standard prefixes: feat(component):, chore:, fix(component):
- Distinctive: line 21
Keep titles concise and descriptive
- Distinctive: line 35
Actionable scope: - should be implementable by a developer familiar with the codebase
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

