gh-issue-replier
Skill326 starsChanged 8 months agoMITView on GitHub
Professional English replier for GitHub issues. Use when a task is completed, a bug is fixed, or more info is needed from the user. Automates replying using the 'gh' CLI tool.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Fu-Jie/openwebui-extensionsword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Fu-Jie/openwebui-extensions★ 326100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- community-announcerSkill
- doc-mirror-syncSkill
- gh-discussion-replierSkill
- gh-issue-schedulerSkill
- i18n-validatorSkill
- playwright-openwebuiSkill
- plugin-scaffolderSkill
- pr-reviewerSkill
- pr-submitterSkill
- publish-no-version-bumpSkill
- release-finalizerSkill
- release-prepSkill
- source-code-analyzerSkill
- version-bumperSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Distinctive: line 15
Check Star Status: Run the bundled script to check if the author has starred the repo.
- Very specific: line 22
Post the Comment: Use the gh tool to submit the reply.
- Distinctive: line 48
Language: ALWAYS use English for the comment body, even if the system prompt or user conversation is in another language.
- Distinctive: line 50
Precision: When announcing a fix, mention the specific version or the logic change (e.g., "Updated regex pattern").
- Very specific: line 51
Closing: If the issue is resolved and you have permission, you can also use gh issue close <number>.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Gh Issue Replier
Overview
The gh-issue-replier skill enables Gemini CLI to interact with GitHub issues professionally. It enforces English for all communications and leverages the gh CLI to post comments.
Workflow
- Identify the Issue: Find the issue number (e.g., #49).
- Check Star Status: Run the bundled script to check if the author has starred the repo.
- Command:
bash scripts/check_star.sh <issue-number> - Interpretation:
- Exit code 0: User has starred. Use "Already Starred" templates.
- Exit code 1: User has NOT starred. Include "Star Request" in the reply.
- Command:
- Select a Template: Load templates.md to choose a suitable English response pattern.
- Draft the Reply: Compose a concise message based on the star status.
- Post the Comment: Use the
ghtool to submit the reply.
Tool Integration
Check Star Status
bash scripts/check_star.sh <issue-number>Post Comment
gh issue comment <issue-number> --body "<message-body>"Example (if user has NOT starred):
gh issue comment 49 --body "This has been fixed in v1.2.7. If you find this helpful, a star on the repo would be much appreciated! ⭐"Example (if user HAS starred):
gh issue comment 49 --body "This has been fixed in v1.2.7. Thanks for your support!"Guidelines
- Language: ALWAYS use English for the comment body, even if the system prompt or user conversation is in another language.
- Tone: Professional, helpful, and appreciative.
- Precision: When announcing a fix, mention the specific version or the logic change (e.g., "Updated regex pattern").
- Closing: If the issue is resolved and you have permission, you can also use
gh issue close <number>.
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.