GH Issue Commenter
Apps & Automationgh-issue-commenterGH Issue Commenter is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Comment on GitHub issues using the gh CLI. Use when Codex needs to share an implementation plan, progress update, or blockers. Always read the issue body and comments for context, optionally read related issues, and only create or update Codex-owned comments.
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/majiayu000/claude-skill-registry/blob/HEAD/skills/development/gh-issue-commenter/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gh-issue-commenter, 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.
GitHub Issue Commenter
Create or update a single Codex-owned issue comment for plans, progress, or blockers. Keep comments concise and precise; use Markdown headings and code blocks for snippets.
Workflow
- Identify the issue number (using skills or user input).
- Read the issue body and existing comments for context:
gh issue view <issue-number> --comments
- If the issue references related issues (e.g.,
#123or links), read them as needed:gh issue view <related-issue-number> --comments
- Draft the comment with a stable marker so only Codex-owned comments are edited.
- Create or update the Codex-owned comment using the script:
.codex/skills/gh-issue-commenter/scripts/issue_comment_sync.sh <issue-number> <body-file> [--commenter <login>]
Comment Format
Start every comment with the marker on its own line:
<!-- CODEX:gh-issue-commenter -->
Then use a compact structure appropriate to the update type.
Plan
<!-- CODEX:gh-issue-commenter -->
**Plan**
1. ...
2. ...
Progress
<!-- CODEX:gh-issue-commenter -->
**Progress**
- ...
**Next**
- ...
Blockers
<!-- CODEX:gh-issue-commenter -->
**Blockers**
- ...
**Needs**
- ...
Constraints
- You MUST read the issue body and comments before posting.
- You MUST only create or edit Codex-owned comments (identified by the marker).
- You SHOULD keep the comment concise and focused.
- You MAY split updates into multiple sections if it improves clarity.
- If
--commenteris used, it MUST be the GitHub login used to locate the Codex-owned comment to update.