github-issue-manager
Skill2 starsChanged 17 days agoApache-2.0View on GitHub
Create GitHub issues and development branches. Use when the user wants to start work on a bug, feature (enhancement), or documentation task and needs a structured way to track it.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Onlyaguest/ViviStableSkillstheir own version, first seen Oct 10, 2026
- pass-with-high-score/ANekotheir own version, first seen Oct 8, 2026
- pass-with-high-score/universal-installertheir own version, first seen Oct 8, 2026
- pass-with-high-score/blockads-androidtheir own version, first seen Oct 8, 2026
- apetrov/skillstheir own version, first seen Mar 19, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- pass-with-high-score/blockads-android★ 2.7ksame name
- pass-with-high-score/universal-installer★ 1.7ksame name
- pass-with-high-score/ANeko★ 583same name
- Onlyaguest/ViviStableSkills★ 18same name
- apetrov/skills★ 0same name
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 repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- git-workflow-lifecycleSkill
- release-managerSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
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
- Very specific: line 12
Create Issue & Branch: Run the manage_issue.py script to create a GitHub issue with appropriate labels and switch to a new branch.
- Very specific: line 37
Analyze Report: Read results in .gemini/skills/github-issue-manager/evals/reports/latest_results.json.
- Very specific: line 39
Attempt 1: If any checks FAIL (e.g., branch not created, issue missing), analyze the error and attempt to fix the issue.
- Distinctive: line 41
Escalation: If still failing after 2 attempts, stop and present the failure report to the user.
“Common” is measured: kept by at least 6 in 10 of the 5 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 Manager
This skill automates the creation of GitHub issues and the setup of local development branches.
Workflow
- Create Issue & Branch: Run the
manage_issue.pyscript to create a GitHub issue with appropriate labels and switch to a new branch.python3 .gemini/skills/github-issue-manager/scripts/manage_issue.py "Title" "Description" --type <bug|enhancement|documentation>
Instructions
- Issue Types:
bug: For reporting errors or unexpected behavior.enhancement: For new features or improvements.documentation: For updates to READMEs, guides, or site content.
- Branch Naming: The script generates a concise branch name in the format
type/abbreviated-title.enhancementmaps tofeature/bugmaps tobug/documentationmaps todocumentation/
- Requirements: Requires the
gh(GitHub CLI) to be installed and authenticated.
Scripts
scripts/manage_issue.py: The core automation script.
Self-Evaluation & Correction
You MUST autonomously verify every issue management task:
- Run Evaluation Suite:
python3 .gemini/skills/github-issue-manager/evals/runner.py <issue_type> "<title>" - Analyze Report: Read results in
.gemini/skills/github-issue-manager/evals/reports/latest_results.json. - Self-Correction Loop:
- Attempt 1: If any checks
FAIL(e.g., branch not created, issue missing), analyze the error and attempt to fix the issue. - Attempt 2: One final targeted fix and re-run.
- Attempt 1: If any checks
- Escalation: If still failing after 2 attempts, stop and present the failure report to the user.
<AVAILABLE_RESOURCES>
- Evaluation Runner:
.gemini/skills/github-issue-manager/evals/runner.py</AVAILABLE_RESOURCES>
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.

