GH Issue Replier
Apps & Automationgh-issue-replierGH Issue Replier is an Agent Skill for apps & automation published in the Fu-Jie/openwebui-extensions repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Fu-Jie/openwebui-extensions/blob/HEAD/.agent/skills/gh-issue-replier/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gh-issue-replier, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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>.