gh-issue
Skill2 starsChanged 42 days agoMITView on GitHub
Create a GitHub issue for a bug or feature idea found during an agent session
11 other projects use a version of this.
Adopted by
Most recently taken up by
- ukchucktown/agent-skillstheir own version, first seen Nov 1, 2026
- apache/skywalking-banyandbtheir own version, first seen Oct 9, 2026
- hunghg255/reactjs-tiptap-editortheir own version, first seen Oct 8, 2026
- gittower/git-flow-nexttheir own version, first seen Oct 8, 2026
- jocmp/capyreadertheir own version, first seen Oct 8, 2026
- latitude-dev/latitude-llmtheir own version, first seen Oct 8, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- latitude-dev/latitude-llm★ 4.7ksame name
- jocmp/capyreader★ 1.5ksame name
- hunghg255/reactjs-tiptap-editor★ 749same name
- gittower/git-flow-next★ 458same name
- apache/skywalking-banyandb★ 355same name
- Hey-Diga/dotclaude★ 17same name
- Cogni-AI-OU/cogni-ai-agent-skills★ 4same name
- zazzcode/zazz-skills★ 4same name
- grantkee/claude-extensions★ 2same name
- ukchucktown/agent-skills★ 1same name
1 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- changelog-bump-verSkill
- gh-copilot-review-readSkill
- gh-copilot-review-resolveSkill
- gh-copilot-reviewSkill
- gh-cr-submitSkill
- gh-issue-fixSkill
- gh-pr-mergeSkill
- gh-protect-default-branchSkill
- gh-pr-reviewSkill
- gh-prSkill
- gh-releaseSkill
- git-branchSkill
- git-commitSkill
- git-pushSkill
- make-changelogSkill
- mir-skills-installSkill
- mir-skills-updateSkill
- python-venvSkill
- save-planSkill
- session-noteSkill
- work-reportSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Ask user if this is a bug or feature request (if not already stated)
- Very specific: line 16
Create the issue via gh issue create and return the URL
- Distinctive: line 20
Use this skill when:
- Distinctive: line 27
Must be inside a git repo with a GitHub remote
- Very specific: line 28
If gh not installed → error: "Error: GitHub CLI not found.
- Distinctive: line 29
If no GitHub remote found → error: "Error: No GitHub remote found.
- Distinctive: line 34
If user did not specify → ask: "Is this a bug or a feature request?"
- Distinctive: line 41
Body: use the 3-field format below
- Distinctive: line 69
No period at end
- Distinctive: line 74
Keep the entire body under 5 sentences total
- Very specific: line 81
No GitHub remote → "Error: No GitHub remote found.
“Common” is measured: kept by at least 6 in 10 of the 10 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
What I do
- Ask user if this is a bug or feature request (if not already stated)
- Draft a concise, AI-agent-readable title and body from session context
- Apply
bugorenhancementlabel (GitHub creates it if missing) - Create the issue via
gh issue createand return the URL
When to use me
Use this skill when:
- User discovers a bug or has a feature idea during a session
- User wants to log it as a GitHub issue without losing the session context
Prerequisites
- GitHub CLI (
gh) must be installed and authenticated - Must be inside a git repo with a GitHub remote
- If
ghnot installed → error: "Error: GitHub CLI not found. Install: https://cli.github.com/" - If no GitHub remote found → error: "Error: No GitHub remote found. Is this a GitHub repository?"
Workflow
- Determine issue type
- If user did not specify → ask: "Is this a bug or a feature request?"
- Map to label: bug →
bug, feature request →enhancement
- Draft the issue from session context
- Title: short, imperative, ≤60 chars
- Bug examples:
Fix null pointer in auth handler,Handle empty state in user list - Feature examples:
Add dark mode toggle to settings,Support CSV export for reports
- Bug examples:
- Body: use the 3-field format below
- Label:
bugorenhancement
- Title: short, imperative, ≤60 chars
- Validate prerequisites
gh auth status git remote get-url origin - Create the issue
gh issue create --title "<title>" --label "<bug|enhancement>" --body "<body>" - Return the issue URL to the user
Issue Body Format
**Type:** Bug | Feature Request
**Context:** <1-2 sentences — what was happening in the session when this was found>
**Description:** <What needs to be done, written concisely for an AI agent to act on later>Title Guidelines
- Imperative mood, present tense (e.g. "Fix", "Add", "Support", "Handle")
- ≤60 characters
- No period at end
- Specific enough for an AI agent to understand the scope without extra context
Body Guidelines
- Keep the entire body under 5 sentences total
- Context: what triggered this — what the agent/user was doing when the issue was discovered
- Description: actionable and self-contained — an AI agent should be able to open this issue cold and know what to do
Error Handling
ghnot installed →"Error: GitHub CLI not found. Install: https://cli.github.com/"- No GitHub remote →
"Error: No GitHub remote found. Is this a GitHub repository?" - Not authenticated →
"Error: Not authenticated with GitHub. Run: gh auth login" - Insufficient context to draft the issue → ask the user to describe it in 1-2 sentences
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.

