post-issue-comment — Claude Code skill: use and install
This skill reads a GitHub issue, drafts a concise English reply, and posts it. Use it when the response needs to reflect the existing discussion.
npx skills add dyoshikawa/rulesync --skill post-issue-comment -a claude-codeWhat post-issue-comment does
The skill takes an issue number or URL together with the point the reply should make. When either part is missing, it asks for clarification. It then fetches the issue description, metadata, and comments with gh issue view, and can inspect related pull requests, commits, or files when they matter.
It drafts a concise English comment and sends it with gh issue comment <issue_number> --body "<reply body>". The reply follows the discussion, preserves the user's position, and avoids adding claims the user did not request. Plain paragraphs are preferred over headings, horizontal rules, and long bullet lists.
The posting step depends on GitHub CLI being available in PATH. When the discussion lacks enough context for a decision, the skill says so in the reply instead of guessing.
What it helps with
- gather a GitHub issue's description and comments
- check the latest discussion before replying
- turn a user's intent into an English comment
- post the drafted reply to the issue
Example prompts for the agent
- Read the GitHub issue I specify and post a short reply that agrees with the proposal and asks for a test.
- Review the issue discussion, explain politely why the proposed change does not fit, and mention the related files.
- Use my intent to draft an English reply to the issue, then publish the comment.
How to install post-issue-comment
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-issue-comment -a claude-code2Manually: put the files in place
~/.claude/skills/post-issue-comment/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/post-issue-comment/
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-issue-comment -a codex2Manually: put the files in place
.agents/skills/post-issue-comment/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-issue-comment -a cursor2Manually: put the files in place
.cursor/skills/post-issue-comment/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dyoshikawa/rulesync post-issue-comment2Manually: put the files in place
.github/skills/post-issue-comment/SKILL.md1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-issue-comment -a gemini-cli2Platform CLI
gemini skills install https://github.com/dyoshikawa/rulesync --path .rulesync/skills/post-issue-commentManually: put the files in place
.devin/skills/post-issue-comment/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-issue-comment -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about post-issue-comment
How do I install post-issue-comment in Claude Code?
Run npx skills add dyoshikawa/rulesync --skill post-issue-comment -a claude-code, then check ~/.claude/skills/post-issue-comment/SKILL.md.
What does post-issue-comment do?
It gathers GitHub issue context, turns the user's intent into a concise English reply, and posts that reply through GitHub CLI.
What does post-issue-comment need to publish a comment?
It runs gh issue view and gh issue comment, so GitHub CLI must be available. The request also needs the target issue and the point the reply should convey.
Source text
SKILL.md · MIT
--- name: post-issue-comment description: >- Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments targets: - "*" --- arguments = the user's request Parse `arguments` as: - `target_issue`: the issue number (or URL) to reply to - `intent`: the gist of the reply the user wants to post (what to say, the stance to take, the points to cover) If `target_issue` is not provided, ask the user which issue to comment on. If `intent` is not provided, ask the user what the reply should convey. ## Step 1: Gather Issue Context Run the following in parallel: - Get the issue description and metadata: `gh issue view <issue_number>` - Get the issue comments: `gh issue view <issue_number> --comments` If the issue references related pull requests, commits, or files that are needed to craft an informed reply, gather that context as well. ## Step 2: Draft the Reply Based on the issue content and the user's `intent`, draft a reply comment. - Ground the reply in the actual discussion — address the latest comment or the original issue as appropriate. - Reflect the user's `intent` faithfully; do not add positions the user did not ask for. - If relevant context is missing or a decision cannot be made without more information, say so in the reply rather than guessing. ## Step 3: Post the Comment Post the drafted reply using: ```bash gh issue comment <issue_number> --body "<reply body>" ``` ## Writing Style Write in **English only**. Style guidelines — write like a human teammate, not a bot: - Use plain paragraphs. Avoid headings (`##`), horizontal rules (`---`), and excessive bullet lists. - Keep it conversational and direct. Say what matters, skip the filler. - Do not use phrases like "Great point!" or "Thanks for raising this!" unless you genuinely mean it and have nothing else to add. - Be honest. If you disagree or see an issue, say so clearly but respectfully. - Short is fine. A two-sentence comment is better than a five-paragraph essay with no substance. ## Step 4: Report Output the issue number and a brief summary of the comment that was posted.
© dyoshikawa · MIT · dyoshikawa/rulesync