github-issues
Skill0 starsChanged 8 months agoApache-2.0View on GitHub
Guide for writing effective GitHub issues — what to include, what to exclude, and common mistakes
52 other projects use a version of this.
Adopted by
Most recently taken up by
- fmind/dottheir own version, first seen Nov 8, 2026
- fmind/dotfilestheir own version, first seen Nov 8, 2026
- devantler-tech/ksailtheir own version, first seen Nov 7, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
- ethosagent/ethostheir own version, first seen Nov 3, 2026
- github/awesome-copilottheir own version, first seen Oct 25, 2026
Used with
Projects with it also use github-repo-management, native-mcp and 10 more.
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.
math-incSkillgithub-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
Also in 13 projects that use this
- math-incSkill
native-mcp
Built-in MCP (Model Context Protocol) client that connects to external MCP servers, discovers their tools, and registers them as native Gauss Agent tools. Supports stdio and HTTP transports with automatic reconnection, security filtering, and zero-config tool injection.
Also in 8 projects that use this
john-data-chenSkilltouchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
Also in 5 projects that use this
Tommy-ywSkillwebhook-subscriptions
Create and manage webhook subscriptions for event-driven agent activation, or for direct push notifications (zero LLM cost). Use when the user wants external services to trigger agent runs OR push notifications to chats.
Also in 4 projects that use this
- Tommy-ywSkill
songwriting-and-ai-music
Songwriting craft, AI music generation prompts (Suno focus), parody/adaptation techniques, phonetic tricks, and lessons learned. These are tools and ideas, not rules. Break any of them when the art calls for it.
Also in 8 projects that use this
- +7 more from math-inc
Other versions52 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 52
- github/awesome-copilot★ 41ksame name
- TypeCellOS/BlockNote★ 10ksame name
- vladmandic/sdnext★ 7.4ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- Lilac-Labs/gini-agent★ 1.9ksame name
- Open-Curiosity/gini-agent★ 1.9ksame name
- math-inc/OpenGauss★ 1.3ksame name
- benchmark-action/github-action-benchmark★ 1.3ksame name
- trezor/trezor-suite★ 1.1ksame name
42 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 repository4 other files it gives its agents.
- design-docsSkill
- python-styleSkill
- tddSkill
- test-desiderataSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Keep it skimmable—use lists, not paragraphs
“Common” is measured: kept by at least 6 in 10 of the 51 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
Essential sections
Title — Concise, specific. "ux: make the CLI delightful" not "CLI Improvements"
Problem — What's broken? Who experiences it? What's the impact?
Proposed Solution — What needs to happen? Keep it at the what level, not the how.
What to include vs. exclude
Include: Commands, flags, user-facing behaviors, error scenarios.
Exclude: Implementation details (libraries, frameworks, file structure), code examples, "Implementation Notes" sections.
Good practices
- Be concise. Cut the fluff.
- Describe the what, not the how
- Focus on user experience, not architecture
- One clear problem statement
- Keep it skimmable—use lists, not paragraphs
Common mistakes
- Adding implementation suggestions (frameworks, libraries)
- Including example output/code
- Writing "Implementation Notes" or "Technical Details"
- Too much structure (nested sections, elaborate formatting)
- Prescribing solutions instead of describing problems
- Verbose explanations of obvious things
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.